window.onUnload don't work when the page is in a popup
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: matutetandil, Unassigned)
References
Details
(Keywords: regression)
Attachments
(2 files)
![]() |
||
Comment 3•13 years ago
|
||
![]() |
||
Comment 6•13 years ago
|
||
![]() |
||
Comment 7•13 years ago
|
||
Comment 10•12 years ago
|
||
Comment 11•12 years ago
|
||
Comment 12•10 years ago
|
||
Comment 14•9 years ago
|
||
Comment 15•9 years ago
|
||
Comment 16•9 years ago
|
||
Comment 17•9 years ago
|
||
Comment 18•9 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Comment 19•3 years ago
|
||
I can't manage to reproduce this issue on my machines Win 10 and MacOS 11 on the latest Nightly. No alerts message received from accessing the html from the description and close both pages(pop-up and first page). Same behaviour on Chrome. Maybe the test case(html) should be updated.
Alice, is this issue still reproducible on the latest Nightly?
I noticed that Matias account is not active anymore.
Thanks.
![]() |
||
Comment 20•3 years ago
|
||
Steps to reproduce:
- Open
Browser Console
(Ctrl+Shift+Alt+I) and EnableShow Content Messages
- Open attached Bug681636-p.html in a new tab
- Close the tab
Actual Results:
Browser Console
does not output unload event detected!
.
Expected Results:
Browser Console
should output unload event detected!
.
Comment 21•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Updated•2 years ago
|
Comment 22•2 years ago
|
||
The problem with the example in comment 20 is that the console.log
API doesn't record the log
call from the unload handler. An XHR triggered from the unload handler with the same STR does work, though, and triggers browser console output.
Description
•