Note that there are some explanatory texts on larger screens.

plurals
  1. POFlash Of Unstyled Content (FOUC) in Firefox 3.5+
    text
    copied!<p>We've reached the end of our tether here trying to overcome a nasty and intermittent FOUC in Firefox 3.5.x+ for a new release we're working on.</p> <p>We've tried:</p> <ul> <li>Disabling Javascript in FF</li> <li>Using Quirks mode rendering by removing the DOCTYPE</li> <li>Moving from <code>@import</code> for additional CSS to <code>&lt;link&gt;</code></li> <li>Switching concatenation on and off</li> <li>Removing CSS files from the concat, one at a time</li> <li>Switching the local cache off in Firefox</li> <li>etc</li> </ul> <p>Our previous release never exhibited any FOUC issues, so it's something we've done to this release. Changes we've made so far include:</p> <ul> <li>Using Base64 encoded images over Data URIs for all decorative imagery, served via CSS.</li> <li>Separating 'framework'-related CSS files from page-specific CSS and bundling them as two separate CSS files</li> </ul> <p>To recreate the problem... use Firefox 3.5.x or 3.6.x, then:</p> <ol> <li>Head on over to: <a href="http://my.publisher-subdomain.env.yola.net/" rel="nofollow">http://my.publisher-subdomain.env.yola.net/</a></li> <li>Login with username: 'stack@yola.com' and password: 'stackoverflow'</li> <li>Once logged-in, you should be at <a href="http://my.publisher-subdomain.env.yola.net/sites/" rel="nofollow">http://my.publisher-subdomain.env.yola.net/sites/</a></li> <li>Click the Account link in the main nav.</li> <li>The Account page should load, and you should see a FOUC. If the FOUC does not occur, clear your cache and reload the page.</li> </ol> <p>Your help would be greatly appreciated! :)</p> <p><strong>UPDATE:</strong></p> <p>The dev environment is still exhibiting the FOUC, but only if FireFox is running low on memory or has a lot of extensions installed. Latency and rendering speed definitely affect the visibility of this FOUC.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload