Bug 95794

Summary: [chromium] beforeunload handlers in iframes only fire if there is a top-level beforeunload handler
Product: WebKit Reporter: Ojan Vafai <ojan>
Component: UI EventsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: abarth, ap, beidson, creis, fishd, rniwa, schenney, tony
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
test case without top-level handler
none
testcase with top-level handler none

Ojan Vafai
Reported 2012-09-04 16:15:20 PDT
Will add test-cases. Tested in Chrome 23.0.1246.0 (Official Build 153452) dev on Linux. Not sure if this happens in non-Chrome WebKits.
Attachments
test case without top-level handler (278 bytes, text/html)
2012-09-04 16:15 PDT, Ojan Vafai 		no flags
Details
testcase with top-level handler (354 bytes, text/html)
2012-09-04 16:16 PDT, Ojan Vafai 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ojan Vafai
Comment 1 2012-09-04 16:15:44 PDT
Created attachment 162120 [details] test case without top-level handler
Ojan Vafai
Comment 2 2012-09-04 16:16:54 PDT
Created attachment 162122 [details] testcase with top-level handler
Ojan Vafai
Comment 3 2012-09-04 16:17:35 PDT
Actually, looks like we fire the unload handlers in both cases if you hit reload, but not if you close the tab.
Alexey Proskuryakov
Comment 4 2012-09-05 09:56:28 PDT
Appears to work as expected in Safari 6.
Ojan Vafai
Comment 5 2012-09-05 10:00:29 PDT
Seems likely that we're just not propagating the hasUnloadHandlers bit up to the browser process on the Chrome side. Will remove the chromium prefix on the bug summary if it turns out to be a generic webkit issue.
Ryosuke Niwa
Comment 6 2012-09-13 11:19:39 PDT
(In reply to comment #5) > Seems likely that we're just not propagating the hasUnloadHandlers bit up to the browser process on the Chrome side. Will remove the chromium prefix on the bug summary if it turns out to be a generic webkit issue. Sounds like this is an issue in Chromium codebase?
Note You need to log in before you can comment on or make changes to this bug.