Partial restoration of closed windows with 'Reopen all windows' option in History menu
Categories
(Firefox :: Session Restore, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox124 | --- | wontfix |
firefox125 | --- | wontfix |
firefox126 | --- | wontfix |
firefox127 | --- | verified |
People
(Reporter: epopescu, Assigned: sfoster)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-session-restore])
Attachments
(1 file)
Found in
- Firefox 125.0b8
Affected versions
- Nightly 126.0a1
- Firefox 124.0.2
- Firefox 125.0b8
Tested platforms
- Affected platforms: All
- Unaffected platforms: None
Steps to reproduce
- Open Firefox using a new profile
- Use the "New Window" option from the side menu to open several new windows(three in this instance)
- Close all previously opened windows except one
- Use the "Reopen all windows" option from History > Recently closed windows
Expected result
- All previously closed windows are restored.
Actual result
- Only two windows are restored out of the three previously closed when using the "Reopen all windows" option from History > Recently closed windows.
Regression range
Regression range narrowed down to:
- Last good revision: db66b8bc0dca08a4b3c1864ee10fc7c903071f88
- First bad revision: 0df1e23ae51110611b7429b661209b84916d0203
- Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=db66b8bc0dca08a4b3c1864ee10fc7c903071f88&tochange=0df1e23ae51110611b7429b661209b84916d0203
However, I'll double-check before confirming the culprit to be Bug 1819675.
Reporter | ||
Updated•6 months ago
|
Reporter | ||
Comment 1•6 months ago
|
||
I've double-checked the regression range for this issue, and it seems that the same culprit, Bug 1819675, has appeared
Comment 2•6 months ago
|
||
:sfoster, since you are the author of the regressor, bug 1819675, could you take a look?
For more information, please visit BugBot documentation.
Updated•6 months ago
|
Assignee | ||
Comment 3•6 months ago
|
||
Thanks for tracking down the regressor.
Updated•6 months ago
|
Comment 4•5 months ago
|
||
Set release status flags based on info from the regressing bug 1819675
Updated•5 months ago
|
Comment 5•5 months ago
|
||
Sam, is that a bug that will get fixed in 127? Thanks
Assignee | ||
Comment 6•5 months ago
|
||
Updated•5 months ago
|
Assignee | ||
Comment 7•5 months ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #5)
Sam, is that a bug that will get fixed in 127? Thanks
Yes! I've put a patch on here for review. Its pretty simple, I don't anticipate any issue getting it into 127.
Comment 9•5 months ago
|
||
bugherder |
Reporter | ||
Comment 10•5 months ago
|
||
I've replicated this issue using 126.0a1 (2024-04-05) on Windows 10 x64.
Verified as fixed in the latest Nightly 127.0a1 version on Windows 10 x64, macOS 13, and Ubuntu 22.04, as the issue no longer occurs.
Description
•