Beforeunload prompt isTabModalPromptAllowed check broken
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
People
(Reporter: pbz, Unassigned)
References
Details
In PromptCollection.asyncBeforeUnloadCheck
, the check for contentViewer.isTabModalPromptAllowed
does not work, since contentViewer
is always null
.
I'm assuming that's because the docshell associated with the browsing context is not accessible from the parent process?
Comment 1•4 years ago
|
||
That shouldn't be a problem. It's expected in the out-of-process case, which is why we check the BrowsingContext instead when there isn't a content viewer.
Comment 2•4 years ago
|
||
Set release status flags based on info from the regressing bug 1655866
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
Doesn't this flag have a different meaning? Looking at the getter it returns the visibility state of the content viewer: https://searchfox.org/mozilla-central/rev/d25eb00ab4e90cc0130cd18f303a04cc2a2f8409/layout/base/nsDocumentViewer.cpp#3756
Could you please elaborate on why we don't need to check it in the out-of-process case? I assume that is the common case.
Thanks!
Comment 4•4 years ago
|
||
(In reply to Paul Zühlcke [:pbz] from comment #3)
Doesn't this flag have a different meaning? Looking at the getter it returns the visibility state of the content viewer: https://searchfox.org/mozilla-central/rev/d25eb00ab4e90cc0130cd18f303a04cc2a2f8409/layout/base/nsDocumentViewer.cpp#3756
No, the two checks have the same effect.
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Kris, do we care about this regression for 83? Thanks
Reporter | ||
Comment 6•4 years ago
|
||
(In reply to Kris Maglione [:kmag] from comment #4)
(In reply to Paul Zühlcke [:pbz] from comment #3)
Doesn't this flag have a different meaning? Looking at the getter it returns the visibility state of the content viewer: https://searchfox.org/mozilla-central/rev/d25eb00ab4e90cc0130cd18f303a04cc2a2f8409/layout/base/nsDocumentViewer.cpp#3756
No, the two checks have the same effect.
Thanks! In this case the bug is invalid. However, we should discuss whether it makes sense to keep both flags or to skip prompting in these situations altogether in Bug 1666374.
Description
•