Bug 36051

Summary: unload event not fired when a javascript: URL document unloads
Product: WebKit Reporter: Marc Bonnier <chrome>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ap, beidson
Priority: P3    
Version: 528+ (Nightly build)   
Hardware: Mac (Intel)   
OS: OS X 10.6   
Attachments:
Description Flags
Test case none

Marc Bonnier
Reported 2010-03-12 00:28:59 PST
Created attachment 50581 [details] Test case When a window is loaded with a JSURL, the window uload event is not fired when another JSURL is loaded over it.
Attachments
Test case (769 bytes, text/html)
2010-03-12 00:28 PST, Marc Bonnier 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2010-03-12 21:02:57 PST
Confirmed with r55339. Also, an assertion fails when reproducing this bug: ASSERTION FAILED: item->documentSequenceNumber() == history()->currentItem()->documentSequenceNumber() (/Users/ap/Safari/OpenSource/WebCore/loader/FrameLoader.cpp:3702 void WebCore::FrameLoader::navigateWithinDocument(WebCore::HistoryItem*)) It seems unrelated, but I don't know if it's important.
Brady Eidson
Comment 2 2010-03-12 22:40:40 PST
Is the unload event supposed to fire...?
Brady Eidson
Comment 3 2010-03-12 22:40:57 PST
ASSERT failure is interesting, though.
Alexey Proskuryakov
Comment 4 2010-03-12 23:16:39 PST
I think it supposed to fire, yes. I was going to suggest opening a new bug for the assertion failure, but now I think there's a chance it could theoretically have same root cause.
Note You need to log in before you can comment on or make changes to this bug.