Interesting. That's a very good point that seems to argue in favor of keeping
the distinction between the selector matching/cascading functions and the flow
construction functions that we have, and making any optimization that combines
the two passes operate at a higher level (as I was figuring
On 2/9/14 1:24 PM, Patrick Walton wrote:
(2) it's easier to benchmark
style recalc against Gecko and WebKit when it's not intertwined with
intrinsic width calculation.
One note here. It's not uncommon for pages to do things that need a
style recalc (e.g. a getComputedStyle() call) but don't n
(Copy and paste from GitHub issue #1650 because I figure mailing list
discussion is potentially more fruitful than GitHub issues for design
discussions.)
I realized this morning that we can probably avoid the need for a leaf
set by intertwining selector matching and flow construction, and flow
3 matches
Mail list logo
