I don't see any shaming in that post, but I'd like to see clip-path moved to the compositor to make this easier https://bugs.chromium.org/p/chromium/issues/detail?id=686074 …
-
-
Replying to @jaffathecake @pcwalton
If a browser can get layout working at 60fps on a cheap phone, that'd be great! Haven't seen it yet though.
1 reply 0 retweets 1 like -
Replying to @jaffathecake
Width and height for absolute position is trivial to hit 60 with. Only problem is main thread jank. That’s why layout should move off it.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
That's making a lot of assumptions about the content of the el. Also, by requiring abs position you're forcing tricks onto the dev again
2 replies 0 retweets 0 likes -
Replying to @jaffathecake
Layout of a menu like that with any reasonable setup will be 60 FPS. It’s static text stacked on top of each other.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
Sure, but that isn't true of all expanding collapsing animations
1 reply 0 retweets 0 likes -
Replying to @jaffathecake
If CSS transforms are enough to replicate the effect, then layout won’t rerun anything expensive on the inside anyway.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
Happy to see Servo trailblaze here. If it can show expanding/collapsing with layout at 60fps on a phone, then yeah, that's game-changing
1 reply 0 retweets 1 like -
Replying to @jaffathecake @pcwalton
I think you'd be replacing one set of tricks for another, especially if you want sub-pixel animations, but I'd be delighted to be wrong here
1 reply 0 retweets 0 likes -
Replying to @jaffathecake @pcwalton
But I still don't see how the article is "shaming" developers.
1 reply 0 retweets 0 likes
Yeah, apologies, that was a poor choice of words for that article.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.