(Windows 10) Abusing confirmation close dialog (Alt+F4) hangs the browser
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
People
(Reporter: aflorinescu, Unassigned)
References
(Regression)
Details
(Keywords: hang, regression)
[Description:]
While tinkering with bug 1720254, I accidentaly realized that abusing the alt+F4 will shortly enter the browser into an unresponsive state.
#####[Environment:]
Windows 10
Ubuntu 20.04.3 - doesn't reproduce
Mac 11.0.4 - doesn't reproduce (@ cmd+Q)
[Steps:]
- New profile, about:preferences#general, enable session restore and warn on close.
- Ctrl+T open several new tabs.
- Forget your fingers on Alt+F4.
[Actual Result:]
The browser hangs, needs to be terminated from task manager.
[Expected Result:]
The browser doesn't hang :)
[Regression Range:]
2021-08-31T18:21:49.381000: DEBUG : Found commit message:
Bug 1685313 - fix tests to pass with either the new or old window modal dialogs, r=jaws
Differential Revision: https://phabricator.services.mozilla.com/D104703
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
I don't think this is S2; I think the STR here are an edgecase. It's basically the Windows version of bug 1705365, which has a patch up that hasn't had review requested, because there are some UX implications. I don't think there is another fix that doesn't have those implications, so I guess I'll follow up there.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•