Le 20/07/2013 04:26, Boris Zbarsky a écrit :
Something else that I forgot to mention during the discussion earlier
today: do we need to worry about the subject indicator stuff Selectors 4
is adding?  Or is that not an issue for rendering/style for now?  The
spec discussion is ... unclear.

Yes, I meant to talk about that as well.

The CSS working group got feedback from some browser implementors (I don’t remember who exactly) that some of the new Selectors Level 4 features are too expensive to used in CSS stylesheets. In particular, (as I understand it,) any change to the DOM tree in presence of such a selector might require to run selector matching again on a big subtree or even the whole document.

However this is not an issue when a selector is only evaluated once, for example in APIs such as document.querySelectorAll(). The spec editors decided to split Selectors 4 into two "profiles" until there is more implementation feedback:

http://dev.w3.org/csswg/selectors4/#profiles

The "complete" profile contains everything, while the "fast" profile contains everything that is not too expensive for dynamic recomputation.

Now, the question is: are these feature intrinsically too expensive to be used in stylesheets evaluated dynamically? Or could we find some clever optimization that makes performance acceptable? Does Servo’s parallelism help compared to mostly single-threaded browsers?

--
Simon Sapin
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo

Reply via email to