@bz_moz sorry. Context is that we often want to load a link[rel=stylesheet] without blocking content rendering. +@hexalys @jaffathecake
-
-
Replying to @scottjehl
@scottjehl@hexalys@jaffathecake At least in Gecko, any <link> outside <head> will not block rendering (but will block scripts after it).2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz Maybe so. Definitely blocks in other browsers (chrome for certain, webkit too I think)@hexalys@jaffathecake1 reply 0 retweets 0 likes -
Replying to @scottjehl
@scottjehl@hexalys@jaffathecake OK, report bugs to them? ;)2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@hexalys@jaffathecake DOM placement to manage request order seems a little odd. We have script[async]. Why not link?2 replies 0 retweets 0 likes -
Replying to @scottjehl
@scottjehl@hexalys@jaffathecake Can you describe what <link async> would do differently from what <link> does? Probably not on twitter...1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz ok. <link href="foo.css" rel="stylesheet"> blocks content rendering until it loads. That's not always desirable. +@jaffathecake1 reply 0 retweets 1 like -
Replying to @scottjehl
@scottjehl@jaffathecake It _sometimes_ blocks content rendering, but OK. Having a way to opt out of that would be trivial, in Gecko.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@jaffathecake my understanding is it blocks if if it is deemed applicable for rendering (media matches, not disabled, not alternate)2 replies 0 retweets 0 likes -
Replying to @scottjehl
@scottjehl@jaffathecake The actual conditions are a lot more complicated, at least in Gecko. For a start, only things in <head> can block.2 replies 0 retweets 0 likes
@scottjehl @jaffathecake Which is why I'm confused by the complaints about <link> at end of <body> and whatnot. ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.