Confirm/alert box disappears when tab moved to different window
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
People
(Reporter: skophek, Unassigned)
References
(Regression)
Details
(Keywords: nightly-community, regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0
Steps to reproduce:
- open some page that shows confirm/alert box and let it display (e.g. https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_alert)
- move tab to another window
Actual results:
alert box + overlay disappears, can't click to anything on the page
Expected results:
alert box stays
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Win32' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
Confirmed on Nightly 120.0a1 (2023-09-29).
Comment 3•1 year ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit BugBot documentation.
Comment 4•1 year ago
|
||
Would be good to know if this was always broken or it regressed at some point.
Comment 5•1 year ago
|
||
The defect #1(alert box disappears) since Firefox4.0.
Regression window for defect #1:
The defect #1 has existed since tab modal dialogs were implemented.
Regressed by: Bug 59314
Whereas, the defect #2(Clicking, keyboard input, and even context menus are not possible in the content area.) the following regression window.
Regression window for defect #2:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3598f96a099133837aa78b6c018ff74ca522e36b&tochange=c5654880057a9011c0d743322b11d2d115ea5fae
Suspect: Bug 1680637
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Set release status flags based on info from the regressing bug 1680637
:mtigley, since you are the author of the regressor, bug 1680637, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 7•1 year ago
|
||
This is basically a dupe of bug 1754759 I think?
Updated•1 year ago
|
Description
•