Suppress event handling for BrowsingContextGroup while spinning event loop in window.open()
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
People
(Reporter: kmag, Assigned: kmag)
References
Details
As a rule, we should always suppress event handling while spinning the event loop, and not doing so here allows for dangerous re-entrancy.
|
||
Comment 1•5 years ago
|
||
Event handling suppression wouldn't help with re-entrancy, since event handling suppression doesn't block all the JS to run.
|
Assignee | |
Comment 2•5 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #1)
Event handling suppression wouldn't help with re-entrancy, since event handling suppression doesn't block all the JS to run.
I know, but it at least blocks some of it (in particular the JS that triggers the problem in bug 1588259). For the rest of it, I think we also need another check specific to window.open, as mentioned in bug 1588259 comment 4.
|
||
Comment 3•5 years ago
|
||
The priority flag is not set for this bug.
:kmag, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Updated•5 years ago
|
|
||
Comment 4•4 years ago
|
||
kmag, you said you have a patch in a different bug. I'd like to dupe this bug to that bug, but what is its bug #?
|
|
Assignee | |
Updated•4 years ago
|
Description
•