3 ms·
You don't need to break the web to implement per-primitive transformations. Safari, FF, IE do them per-primitive for example. The only case when transformation
by c-smile 10y ago
You don't need to break the web to implement per-primitive transformations. Safari, FF, IE do them per-primitive for example.
The only case when transformation are made on bitmap buffers is then 3D transformations are involved. Everyone knows how to do per-primitive 2D transformations these days.
- nostrademons 10y agoPretty sure I still get aliasing artifacts on Safari (and Chrome). Firefox has smooth text but seems to have artifacts on the gradient: https://jsfiddle.net/nqaoq52n/3/ https://jsfiddle.net/nqaoq52n/3/ If I run it through Chrome's Timeline inspector, the majority of the time in each animation frame is spent on the GPU (0.32 ms), while Paint only takes 0.01ms and Composite Layers is 0.03ms (there're also fairly lengthy 0.13ms Recalc Styles and 0.22 Update Layer Tree phases, where I suspect it's walking the whole JSFiddle DOM to find out nothing has changed). If I run it through Firefox's profiler, there is a lengthy Paint (~8ms), followed by only Recalc Styles per animation frame (I'm guessing that it's doing everything on the GPU and the profiler doesn't show me that work), except when the element grows enough to force a scroll bar to appear, which trigger a re-layout.
- pcwalton 10y ago> where I suspect it's walking the whole JSFiddle DOM to find out nothing has changed No browser does this.