[Webkit-unassigned] [Bug 14568] New: load event can fire prematurely for frameless documents
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jul 9 22:44:35 PDT 2007
http://bugs.webkit.org/show_bug.cgi?id=14568
Summary: load event can fire prematurely for frameless documents
Product: WebKit
Version: 522+ (nightly)
Platform: Macintosh
OS/Version: Mac OS X 10.4
Status: NEW
Severity: Normal
Priority: P2
Component: Page Loading
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: ggaren at apple.com
FrameLoader tracks loading progress. Without a FrameLoader, a Document doesn't
know whether loading is in progress. Therefore, a Document might end up
dispatching the load event too early.
This is the responsible code, in Document.cpp:
void Document::close()
{
Frame* frame = this->frame();
if (frame) {
// This code calls implicitClose() if all loading has completed.
FrameLoader* frameLoader = frame->loader();
frameLoader->endIfNotLoadingMainResource();
frameLoader->checkCompleted();
} else {
// Because we have no frame, we don't know if all loading has
completed,
// so we just call implicitClose() immediately. FIXME: This might fire
// the load event prematurely.
implicitClose();
}
}
I don't know if this is a real-world problem or not.
--
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list