Re: [selector-profiles] confusion

On Thursday 2013-07-11 18:46 +0300, Lea Verou wrote:
> Or there could just be a @static rule, with everything inside
> running statically, including fast selectors. Just an idea.

I don't think this works, since either:

 (a) these selectors don't run until the page is loaded completely,
 leaving the page in a broken state until it loads, or

 (b) these selectors run once at some point doing pageload, and thus
 whether they match depends on exactly what the points of
 incremental loading are.  For example, a selector like:
   !.article > h2
 won't match when the network packet boundary happens to come
 between <div class="article"> and <h2>.  This sort of
 nondeterministic behavior is unacceptable; authors won't understand
 it, and will blame the browser, or authors won't even see it, and
 the users will blame the browser.


๐„ž   L. David Baron                  ๐„‚
๐„ข   Mozilla                    ๐„‚

Received on Thursday, 11 July 2013 18:54:47 UTC