Comments on: Rendering styles http://www.phpied.com/rendering-styles/ Stoyan's blog about (x)html, ajax, bookmarklets, browsers, css, firebug, javascript, json, mdb2, mysql, pear, performance, php, phpbb, tools, yslow, yui, writing, music,... life and everything. Sat, 17 May 2008 03:27:26 +0000 http://wordpress.org/?v=2.0.1 by: phpied.com » Blog Archive » Weird attempt for flicker-free rendering solution http://www.phpied.com/rendering-styles/#comment-60671 Sun, 24 Jun 2007 02:02:58 +0000 http://www.phpied.com/rendering-styles/#comment-60671 [...] Another idea - as shown in a previous post, the browsers (except Opera) won't show anything until the last bit of CSS is downloaded. So if you put you big-ass CSS file at the bottom of the page (which is exactly the opposite of what you should be doing when aiming at performance) you might also achieve the desired flicker-free rendering. Post this entry to: » del.icio.us  » Digg  » Furl  » Newsvine  » reddit  » Y! [...] […] Another idea - as shown in a previous post, the browsers (except Opera) won't show anything until the last bit of CSS is downloaded. So if you put you big-ass CSS file at the bottom of the page (which is exactly the opposite of what you should be doing when aiming at performance) you might also achieve the desired flicker-free rendering. Post this entry to: » del.icio.us  » Digg  » Furl  » Newsvine  » reddit  » Y! […]

]]> by: Stoyan http://www.phpied.com/rendering-styles/#comment-60632 Thu, 21 Jun 2007 23:32:18 +0000 http://www.phpied.com/rendering-styles/#comment-60632 Thanks Mytskine for the comment. You're right - Opera does render the page, then re-renders when the first css arrives, the does it again when the second css arrives. I tested again with the latest IE, FF and Safari (on Windows) - they all wait for all css files, before rendering. It makes sense in a way, because re-rendering the page can be expensive and doing it several times in one request is probably something browsers want to avoid. Thanks Mytskine for the comment. You're right - Opera does render the page, then re-renders when the first css arrives, the does it again when the second css arrives.

I tested again with the latest IE, FF and Safari (on Windows) - they all wait for all css files, before rendering. It makes sense in a way, because re-rendering the page can be expensive and doing it several times in one request is probably something browsers want to avoid.

]]> by: Mytskine http://www.phpied.com/rendering-styles/#comment-60631 Thu, 21 Jun 2007 23:23:00 +0000 http://www.phpied.com/rendering-styles/#comment-60631 This article always speaks about "the browser" but in the last paragraphs we learn that it's just FF and IE (which versions?). As far as I know, there are no recommandation of W3C on the subject, so each browser is free to act as it wants to. For instance, have a look at Opera8/9, it behaves differently. And Safari or konqueror or new versions of FF might be smart, too. This article always speaks about "the browser" but in the last paragraphs we learn that it's just FF and IE (which versions?). As far as I know, there are no recommandation of W3C on the subject, so each browser is free to act as it wants to. For instance, have a look at Opera8/9, it behaves differently. And Safari or konqueror or new versions of FF might be smart, too.

]]> by: phpied.com » Blog Archive » Delay loading your print CSS http://www.phpied.com/rendering-styles/#comment-60374 Mon, 18 Jun 2007 03:42:03 +0000 http://www.phpied.com/rendering-styles/#comment-60374 [...] The thing is, when it comes to performance, the browser won't render any part of the page, until all stylesheets are downloaded (fiddled with here). That includes, unfortunately, stylesheets not designed for the currently rendered media. In other words, the browser won't display your page, until the print stylesheet is also downloaded, although it's not used at all for displaying the page. That sucks and should really be addressed in future browser versions. [...] […] The thing is, when it comes to performance, the browser won't render any part of the page, until all stylesheets are downloaded (fiddled with here). That includes, unfortunately, stylesheets not designed for the currently rendered media. In other words, the browser won't display your page, until the print stylesheet is also downloaded, although it's not used at all for displaying the page. That sucks and should really be addressed in future browser versions. […]

]]>