3 ms·
Are you still seeing it on nightly after https://bugzilla.mozilla.org/show_bug.cgi?id=712130 https://bugzilla.mozilla.org/show_bug.cgi?id=712130 was fixed? A b
by bzbarsky 9y ago
Are you still seeing it on nightly after https://bugzilla.mozilla.org/show_bug.cgi?id=712130 https://bugzilla.mozilla.org/show_bug.cgi?id=712130 was fixed?
A bug report with steps to reproduce (even a link to the specific GitHub page involved would help) would be really useful if you are still seeing this. Please cc "bzbarsky". Also worth checking whether the problem persists with extensions disabled, if it's reproducible enough to do that with...
- nachtigall 9y agoThanks I'll file a bug if I see it again on a GitHub page. In fact, the last days I haven't noticed it anymore on GitHub pages... But, of course as stated in https://bugzilla.mozilla.org/show_bug.cgi?id=1404468#c43 https://bugzilla.mozilla.org/show_bug.cgi?id=1404468#c43 there a sites like http://www.jeuxvideo.com/ http://www.jeuxvideo.com/ which huge (1-2sec) FOUC in Firefox (not noticable in Chrome).
- bzbarsky 9y agoYes, that one is on my to-investigate list already. Thank you for the reminder! Chrome has started just blocking the HTML parser completely on stylesheets. That means it doesn't end up with FOUC (except insofar as there is renderable content before a sheet that is affected by the sheet), but at the cost of less parallelism and slower pageload...