Browser support for <link async> sure would give me more time to spend with my family…
-
-
Replying to @scottjehl
Scott Jehl Retweeted Jake Archibald
Or if not that,
@jaffathecake’s suggestion would work https://twitter.com/jaffathecake/status/567007237923934208 … Loading a CSS file without blocking is needlessly complicatedScott Jehl added,
2 replies 1 retweet 6 likes -
Replying to @scottjehl
@scottjehl@jaffathecake I'd be happy with 'defer' on <link>s. Async for CSS isn't viable. 'postpone' was removed from Resources Priorities.1 reply 0 retweets 0 likes -
Replying to @hexalys
@hexalys@jaffathecake I thought async seemed to match the behavior currently implemented for non-applicable stylesheets. Defer could be ok2 replies 0 retweets 1 like -
Replying to @scottjehl
@hexalys any insight into why async isn't viable? It's sort of the pattern we shoot for matching currently (with loadCSS) +@jaffathecake1 reply 0 retweets 0 likes -
Replying to @scottjehl
@scottjehl I argued for it but@bz_moz said it wasn't ok. Thread ref: http://lists.w3.org/Archives/Public/public-web-perf/2013Nov/0008.html … /me Blames the stupid preloader!@jaffathecake4 replies 0 retweets 0 likes
@hexalys @scottjehl @jaffathecake And we could totally add a <link dontblockscripts> or something if that's what the worry is.
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.