RESOLVED CONFIGURATION CHANGED12206
REGRESSION: FOUC posting to blog
https://bugs.webkit.org/show_bug.cgi?id=12206
Summary REGRESSION: FOUC posting to blog
David Kilzer (:ddkilzer)
Reported 2007-01-10 21:20:30 PST
Summary: Seeing FOUC (flash of unstyled content) when I post a comment to a blog entry on mspong.com. Steps to reproduce: 1. Open Safari. 2. Load a blog entry like this one: http://mspong.com/2007/01/09/safari-compatibility/ 3. Post a comment. Expected results: Comment should be posted with no FOUC. Actual results: Comment posted with FOUC. Regression: bdash says, via IRC, that the FOUC isn't as bad in shipping Safari, hence a regression. Notes: Tested with a locally-built debug build of WebKit r18738 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8L127). FOUC seems worse on a slow connection.
Attachments
Maciej Stachowiak
Comment 1 2007-01-29 03:52:09 PST
Dave Hyatt
Comment 2 2007-01-29 15:14:34 PST
I am downgrading the severity of this regression after studying the page. Here is what's happening: (1) In the <head>, a script writes an <img> This forces the early creation of a <body> and a renderer. (2) The Web page even paints. This <img> is width/height of 0, so nothing shows up. (3) The stylesheets are then encountered. We do not allow FOUC suppression after the body has a renderer (meaning painting has happened), and so we FOUC. This is a regression because shipping Safari would allow re-suppression during recalcStyle and would actually destroy renderers. This caused lots of bad bugs like links disappearing during loading. The current behavior is much better. It is very hard to fix this bug I think without detecting that "nothing of substance" was painted.
Frances Cornwall
Comment 3 2024-04-22 20:49:16 PDT
This domain does not exist anymore, but I was able to find this page using the wayback machine at: https://web.archive.org/web/20070323224418/http://mspong.com/2007/01/09/safari-compatibility/. When trying to submit a post using the wayback machine, the page is all white/blank. I don't think we can reproduce this bug anymore. Tested on Safari 17.4.1.
Note You need to log in before you can comment on or make changes to this bug.