User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100902 Firefox/4.0b6pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100902 Firefox/4.0b6pre Summary is enough. Reproducible: Always Steps to Reproduce: 1. Open http://acid3.acidtests.org/ 2. When finished counting up to 97 press the reload button 3. Behold the white rectangle that is visible for a short time and then disappears Actual Results: White rectangle over acid3 test. Expected Results: No white rectangle over acid3 test.
The rectangle also shows when you navigate to another page.
Kai, do you have any regression date for this?
Probably caused by bug 130078.
Status: UNCONFIRMED → NEW
Ever confirmed: true
There is a (transparent) iframe (well actually an object with data attribute that points to an html document) in the acid3 test, which is basically all you need to reproduce this. When we create the content viewer for the new document the mParent pointer on the docshell for the iframe gets nulled out (via the path nsDocShell::CreateContentViewer -> Embed -> SetupNewViewer -> DestroyChildren). But we still draw the old page for a while yet. When we call nsContentUtils::IsChildOfSameType in PresShell::UpdateCanvasBackground (for an opaque bg color on the root content document) and nsSubDocumentFrame::BuildDisplayList (for a container layer on the root content document) it returns null because the parent pointer is null, not because it is the root content document. So I think for drawing purposes, we need to look at the frames/views for this purpose, not the docshell.
Attachment #472503 - Flags: review?(roc) → review+
Created attachment 472786 [details] [diff] [review] patch v2 We need to return a correct value even when we don't have a root frame. The only thing different in this patch is the definition of IsRootContentDocument.
Comment on attachment 472786 [details] [diff] [review] patch v2 Prefer vm over VM
Attachment #472786 - Flags: review?(roc) → review+
blocking2.0: --- → final+
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.