Open Bug 432942 Opened 15 years ago Updated 6 months ago

Add an option to render page immediately without waiting CSS to load


(Firefox :: General, enhancement)






(Reporter: kagesenshi.87, Unassigned)


User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5

some sites might have some of its page data such as CSS on a different server. however, sometimes, the off-site page server might be unavailable / down. 

current firefox keep trying to load that off-site data before rendering the pages which made an impression of slow loading. It would be nice if there are a preferences settings/ about:config entry to change this behaviour so that firefox render the page immediately, ignoring whether CSS is loaded or not.

one example usecase - using google's cache to view contents of a down webserver.

Reproducible: Always

Steps to Reproduce:
1. load a page which its CSS is located in an unreachable server
2. had to wait until for a long timeout to end before content is rendered

Actual Results:  
page rendered - after long~~ time waiting for non-reachable CSS.

Expected Results:  
page rendered immediately
erm .. no .. even with Nglayout.initialpaint.delay set to 1, firefox still tries to load the css before displaying the page

one example (replace with a non-existant computer/IPaddress in ur network):

<link rel="stylesheet" href="" type="text/css"/>
Hello world

try to open it with firefox, and until connection to timed out, firefox does not render the page.
oops .. wrong paste 

<link rel="stylesheet" href="" type="text/css"/>
This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 800 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile,, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Whiteboard: [CLOSEME 2010-11-01]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.