On 1/6/10 5:04 PM, Boris Zbarsky wrote:
I've been doing some more profiling of selector matching and looking at webkit's implementation a bit, and one difference is that they don't have an equivalent of our RuleProcessorData setup: their selector matching uses only data that's available on the node itself, or caches data on the node or on its RenderStyle. In particular, any cache used there persists across possibly multiple style resolutions and is not dynamically allocated.
I lied about the multiple style resolutions thing, at least for the RenderStyle cache. Their RenderStyle is sort of like our nsStyleContext (but not shared between nodes, looks like), and the node gets a new one every time its style is reresolved. Which is why they don't have dynamic update bugs in that stuff, but it also means the cache is only for the duration of a single style resolution.
I don't think that much affects our plan here. ;) -Boris _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
