Bug 36051 - unload event not fired when a javascript: URL document unloads
Summary: unload event not fired when a javascript: URL document unloads
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P3 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-12 00:28 PST by Marc Bonnier
Modified: 2010-03-12 23:16 PST (History)
2 users (show)

See Also:

Attachments
Test case (769 bytes, text/html)
2010-03-12 00:28 PST, Marc Bonnier 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Bonnier 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.
Comment 1 Alexey Proskuryakov 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.
Comment 2 Brady Eidson 2010-03-12 22:40:40 PST 
Is the unload event supposed to fire...?
Comment 3 Brady Eidson 2010-03-12 22:40:57 PST 
ASSERT failure is interesting, though.
Comment 4 Alexey Proskuryakov 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.