Last modified: 2005-01-17 12:08:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 624 - Nested @import causes IE rendering delay
Nested @import causes IE rendering delay
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 640
  Show dependency treegraph
Reported: 2004-10-02 23:11 UTC by Tom Gilder
Modified: 2005-01-17 12:08 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Tom Gilder 2004-10-02 23:11:36 UTC
There is currently a nested import to load the site-wide CSS file. wiki.phtml?title=-
&action=raw&smaxage=0&gen=css is loaded, which contains any preferences-related CSS (such as underlining 
links or not), which then uses @import for the site-wide skin CSS file (such as MediaWiki:Monobook.css).

This causes a huge delay when IE renders the site (unless it has all the CSS cached), because...

 * IE finds a <link> element on the page, so it waits for *all* CSS to download before rendering anything
 * After the first (title=-) stylesheet has loaded, it sends off requests for all page images and other 
external content
 * Only when all images have fully downloaded does it move on to download the site-wide CSS, and only 
then does it render anything

It would be *much* more efficient if the double-@import was killed off. Not only would it speed up IE's 
initial page rendering considerably, it would also save a wasted HTTP request.

Note You need to log in before you can comment on or make changes to this bug.