Two ppl I respect @igrigorik @Souders are giving seemingly contradictory advice. Guys can I ask re: print.css perf. Separate file, good practice or no?
Steve - https://www.stevesouders.com/blog/2010/02/11/mediaprint-stylesheets/ … (old I know but backed up by) https://www.nccgroup.trust/au/about-us/newsroom-and-events/blogs/2018/january/how-to-stop-a-print-stylesheet-slowing-down-your-web-page/ …
Llya -https://developers.google.com/web/fundamentals/performance/critical-rendering-path/render-blocking-css …
-
-
Replying to @benwrighton @Souders
FF blocks rendering on non-matching CSS media query? That seems like a bug if true.. Is there a test URL? /cc
@annevk@bz_moz Re, IE: the fact that nothing changed there is nothing surprising, of course. I assume Edge does not block. /cc@toddreifsteck3 replies 0 retweets 0 likes
Replying to @igrigorik @benwrighton and
Firefox behavior here changed in Firefox 61 to not block rendering on non-matching media. Previous versions blocked rendering (but not parsing. I believe they also blocked following script execution (and hence parsing past it); Firefox 61 does not. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=1386840 …
0 replies
0 retweets
3 likes
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.