- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 11 Jul 2013 11:54:23 -0700
- To: Lea Verou <lea@w3.org>
- Cc: Franรงois REMY <francois.remy.dev@outlook.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Brian Kardell <bkardell@gmail.com>, www-style list <www-style@w3.org>
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. -David -- ๐ L. David Baron http://dbaron.org/ ๐ ๐ข Mozilla http://www.mozilla.org/ ๐
Received on Thursday, 11 July 2013 18:54:47 UTC