Browser intermittently gets stuck in disabled state after cancelling modal dialog with ESC key
Categories
(Toolkit Graveyard :: Notifications and Alerts, defect, P1)
Tracking
(firefox-esr78 unaffected, firefox86 unaffected, firefox87 disabled, firefox88 fixed)
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox86 | --- | unaffected |
firefox87 | --- | disabled |
firefox88 | --- | fixed |
People
(Reporter: pbz, Assigned: pbz)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [proton-modals])
Attachments
(2 files)
+++ This bug was initially created as a clone of Bug #1696793 +++
I can still reproduce a similar issue to Bug 1696793 with the fix applied. The STR are a little bit different and doesn't always happen:
STR:
- Ensure prompts.windowPromptSubDialog = true.
- Close the browser window with quit warning enabled and at least two open tabs.
- Modal dialog appears, press ESC to close it and quickly click the window close button again.
- Quickly repeat step 2 and 3 until the close window button stops to function.
Expected:
Browser continues to operate normally after modal dialog dismissed.
Actual:
Modal dialog goes away but many things stop working, the new tab button is greyed out as well as many menu items. Cannot close window or quit, only apparent way to recover is to terminate the application or close all remaining tabs.
Using these STR I also get a shutdown hang, see Bug 1696397. There are already patches to address this issue, so only the UI disabled issue remains.
Tested on Linux on today's Nightly.
Assignee | ||
Comment 1•4 years ago
|
||
Here is a video showing the issue. Note that this is with the shutdown hang fixes applied. So when closing all tabs the browser shuts down properly.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
I can reproduce it 100% by pressing and holding ESC while clicking the close button.
Comment 4•4 years ago
|
||
Set release status flags based on info from the regressing bug 1685313
Comment 5•4 years ago
|
||
It looks like this is MR1 only, so setting disabled for tracking 87 - let me know if that's wrong.
Comment 6•4 years ago
|
||
Marking as P1. Per experience review we agreed to mark as P1 bug the ones that will block MR1.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 7•4 years ago
|
||
Comment 9•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Updated•1 year ago
|
Description
•