Bug 17717

Summary:

FOUC on mirrordot.org link

Product:

WebKit

Reporter:

David Kilzer (:ddkilzer) <ddkilzer>

Component:

Page Loading

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

bdakin, hyatt, jerome

Priority:

Keywords:

InRadar, NeedsReduction

Version:

523.x (Safari 3)

Hardware:

Mac

OS:

OS X 10.5

URL:

http://www.mirrordot.org/stories/a92bda0b695f8aa3007f1a30bfd3a56e/index.html

Attachments:

Description	Flags
Movie of the FOUC in action	none

David Kilzer (:ddkilzer)

Reported 2008-03-07 18:34:45 PST

* SUMMARY FOUC (flash of unstyled content) when clicking on mirrordot.org links. * STEPS TO REPRODUCE 1. Launch Safari. 2. Go to URL: http://mirrordot.org/ 3. Empty cache with Cmd-Opt-E. 4. Click on any link in the article. (I used <http://mirrordot.org/stories/a92bda0b695f8aa3007f1a30bfd3a56e/index.html> to test.) 5. Do not blink during the page load. * RESULTS FOUC seen briefly while loading the page. * REGRESSION Unknown. *NOTES <rdar://problem/5788297>

Attachments
Movie of the FOUC in action (1.21 MB, video/quicktime) 2009-08-05 10:44 PDT, David Kilzer (:ddkilzer)	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Jerome Leclanche

Comment 1 2009-08-05 10:00:48 PDT

Can't reproduce on 532; site seems to be have been dead since a while.

David Kilzer (:ddkilzer)

Comment 2 2009-08-05 10:38:30 PDT

(In reply to comment #1) > Can't reproduce on 532; site seems to be have been dead since a while. The FOUC still reproduces for me, and the URL still works for me as well.

David Kilzer (:ddkilzer)

Comment 3 2009-08-05 10:44:36 PDT

Created attachment 34147 [details] Movie of the FOUC in action Here's a movie of the FOUC in action while the page is loaded.

David Kilzer (:ddkilzer)

Comment 4 2010-02-16 14:31:42 PST

This appears to be fixed with Safari 4.0.4. Tested on an 8-core Mac Pro running SnowLeopard 10.6.x. Note that all of the links starting with http://mirrordot.org/ need to be changed to http://www.mirrordot.org/.

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