1,192 karma · joined October 2, 2015
I much prefer gaming on consoles because I can't be bothered with all the mental overhead that comes with PC gaming. Like most of us I don't have much time. I turn the console on and I'm instantly playing a version optimised for this hardware. More than happy, even eager, to pay for a version that doesn't have me forever tweaking graphical settings or have me thinking about what the latest advancements in RAM or whatever is.
I'm actually looking forward to Steam Deck as ideally it'll give a much closer to console experience for some PC games I've missed out on.
Edit: I was reminded by another comment that the couch experience of desktop gaming isn't for me either. If I can't operate the whole thing from a gamepad I'm not interested, and last time I gave this a go with a little Lenovo I used for emulation, this still wasn't possible.
At the same time I have noticed that although background-color animations are hardware-accelerated, things like box-shadow actually still aren't, which I was surprised by. Or if they are, blocking the main thread somehow still pauses these animations. At some point I'll do a more extensive example to hash out what is/isn't supported.
I think it's fair enough that there's "spec bugs" and understand the constraints you/they were working in trying to cover both CSS transitions/animations. I prefer browser APIs low level enough to build opinionated libraries around!
Individual transforms for me doesn't go far enough, I haven't been involved in spec discussions but I'm surprised they stopped at transforms and not axes. Think throwing an element - x/y would want different animations based on the gesture velocity. I'm not sure composite works well with transform as its order-dependent, the behaviour is itself not well supported cross browser, though maybe composite+individual transform offers promise in the future.
On the state of implementation in general, I am using this project to file bugs to help get some eyes on WAAPI and so far I've opened 4 in Webkit and none in Blink so there's no worries there :)
Thanks for wpt.fyi - I have bumped into it but I should use it to pre-empt some of these bugs.
The polyfill is just for running tests in Jest. It's actually a little beaten up in terms of implementation and this has worked quite nicely as Chrome even in modern phones seems to not support finished so its helped my polyfill(er)s target those bits too.
Thanks for reaching out, I appreciate it.
2. That is really odd. I'm on a similar machine with no problems. Are these the same demos with the iframe or do you also have problems with the homepage?
Edit: And that CSS Tricks article covers more stuff well.
Another poster has pointed out the play button in examples (which reloads the sandbox iframes) is pushing pages to the browser history. I'll take a look.
My reasoning is more that this is my side project, and I have limited time, and this seems like a good experiment to see if I can make OSS sustainable for once and also allow me to target help (my free time) towards users who are most invested in the project.
In the future I would like to open the repo but it might be tied to hitting a sponsorship amount or perhaps an extra service/product on top for those that want it.