3 ms·
You can take a look at the diffs between this and what the list was in 2011 for Webkit: http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-webkit.html
by nostrademons 11y ago
You can take a look at the diffs between this and what the list was in 2011 for Webkit:
http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-webkit.html http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-...
They look basically the same to me - this part of a browser layout engine hasn't changed much, and probably isn't likely to unless Chrome goes all GPU-rendering. And it includes Webkit browsers as well, so it's also Safari, mobile Safari, Opera, and Android Browser.
- paulirish 11y agoJust FYI: GPU can only used for accelerated compositing (animations) and rasterization (faster paint). We'll need new or async APIs for this stuff to significantly change things at the platform level. In the meantime, we have Virtual DOM and maybe a transactional API for read/write to help alleviate the common cases. Thx for linking up Tony's post btw!