On Fri, Feb 13, 2009 at 12:34 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 9 Feb 2009, Boris Zbarsky wrote:
Ian Hickson wrote:
I'm not convinced either of these are really great solutions. I think it'd
be better just to have the script itself only block when it hits
CSS-dependent APIs
Garrett Smith wrote:
Because you have scripts after your stylesheets, not just stylesheets.
Really, controlled experiments are hard. You have to hold all but one
variable constant.
OK, I modified the example:
http://localhost/jstest/block/link-img-noscript.html
The bottom script will not
Ian Hickson wrote:
On Fri, 13 Feb 2009, Boris Zbarsky wrote:
The current Gecko behavior is that any stylesheet load started by parsing a
style or link tag will increment a counter on the document (well, on a
per-document script loader object, to be more precise). Completion of the load
will
On Sun, Feb 15, 2009 at 9:54 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Garrett Smith wrote:
Because you have scripts after your stylesheets, not just stylesheets.
Really, controlled experiments are hard. You have to hold all but one
variable constant.
OK, I modified the example:
Garrett Smith wrote:
I can see why rule matching would happen for all nodes in the document.
On what occasion(s) do(es) that algorithm run?
Depends on the UA, probably.
For Gecko in particular, any time a stylesheet is added to or removed
from the document, any time a rule is added to or
