Comments on: Saving a HTTP request by combining screen and print styles http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles Web developer Thu, 07 Jan 2010 12:54:44 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Mathias Bynens http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles#comment-72 Mathias Bynens Thu, 07 Jan 2010 12:54:44 +0000 http://www.geertdedeckere.be/?p=35#comment-72 Bramus, and where on that page does it say <code>@media print</code> doesn’t work in IE? Here’s a news flash: <strong>it <em>does</em> work, and has worked since IE 5.5</strong>. The reason it says “Incorrect” in the Trident column / <code>@media</code> support row on that Wikipedia page, is because <a href="http://www.greytower.net/archive/articles/cssmedia.html" rel="nofollow">IE doesn’t fully support all media types specified in CSS2</a> (only <code>all</code>, <code>screen</code> and <code>print</code>). Bramus, and where on that page does it say @media print doesn’t work in IE?

Here’s a news flash: it does work, and has worked since IE 5.5.

The reason it says “Incorrect” in the Trident column / @media support row on that Wikipedia page, is because IE doesn’t fully support all media types specified in CSS2 (only all, screen and print).

]]> By: Bramus! http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles#comment-71 Bramus! Tue, 15 Dec 2009 18:36:27 +0000 http://www.geertdedeckere.be/?p=35#comment-71 And what about or good old pal IE? Yeah, even IE8 can't deal with it well (see http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28Cascading_Style_Sheets%29#Grammar_and_rules) And what about or good old pal IE? Yeah, even IE8 can’t deal with it well (see http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28Cascading_Style_Sheets%29#Grammar_and_rules)

]]> By: Infotech Systems http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles#comment-70 Infotech Systems Mon, 07 Dec 2009 14:46:44 +0000 http://www.geertdedeckere.be/?p=35#comment-70 Is it possible to make a script that will unite all css styles in one file, and then to check for browser type and according to the type of browser select css code in the file? Is it possible to make a script that will unite all css styles in one file, and then to check for browser type and according to the type of browser select css code in the file?

]]> By: Federico Capoano http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles#comment-69 Federico Capoano Mon, 07 Dec 2009 10:29:46 +0000 http://www.geertdedeckere.be/?p=35#comment-69 Hey, cool! Didn't know this. Will it work on every browser? Thanks Hey, cool!
Didn’t know this.
Will it work on every browser?
Thanks

]]> By: Geert De Deckere http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles#comment-65 Geert De Deckere Thu, 11 Jun 2009 08:39:18 +0000 http://www.geertdedeckere.be/?p=35#comment-65 Thanks for your comment, Mathias. Good to hear browsers are going in the direction of only downloading applicable style sheets initially. It is no more than a logical step forward. The article about delay loading print css is interesting; however, requiring javascript to make print styles work is a considerable downside. Thanks for your comment, Mathias. Good to hear browsers are going in the direction of only downloading applicable style sheets initially. It is no more than a logical step forward.

The article about delay loading print css is interesting; however, requiring javascript to make print styles work is a considerable downside.

]]> By: Mathias Bynens http://www.geertdedeckere.be/article/saving-a-http-request-by-combining-screen-and-print-styles#comment-52 Mathias Bynens Fri, 15 May 2009 12:39:23 +0000 http://www.geertdedeckere.be/?p=35#comment-52 You’re right about the reduced amount of HTTP requests; obviously, when you merge two files into one, that’s one request less. However, browser vendors might choose to implement functionality which delays loading separate print stylesheets until after all other resources are loaded. The same would go for any other media type that is not in use at the time the page is loaded. In other words, only stylesheets that were designed for the currently rendered media will be loaded instantly; the other resources can be delayed so they don’t block other downloads. When (if?) that happens, placing screen and print styles in separate files might actually become the better option, since after all, the internet is mostly a screen medium. It will be interesting to see where this goes in the future. Great post! Stoyan Stefanov has <a href="http://www.phpied.com/delay-loading-your-print-css/" rel="nofollow">some more info on the subject</a> — definitely worth a read as well. You’re right about the reduced amount of HTTP requests; obviously, when you merge two files into one, that’s one request less.

However, browser vendors might choose to implement functionality which delays loading separate print stylesheets until after all other resources are loaded. The same would go for any other media type that is not in use at the time the page is loaded. In other words, only stylesheets that were designed for the currently rendered media will be loaded instantly; the other resources can be delayed so they don’t block other downloads.

When (if?) that happens, placing screen and print styles in separate files might actually become the better option, since after all, the internet is mostly a screen medium.
It will be interesting to see where this goes in the future.

Great post! Stoyan Stefanov has some more info on the subject — definitely worth a read as well.

]]>