Restore Last Closed Tab doesn't restore tab in another window if there are no tabs to restore in the current window
Categories
(Firefox :: Session Restore, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | fix-optional |
firefox130 | --- | wontfix |
firefox131 | --- | fix-optional |
firefox132 | --- | affected |
People
(Reporter: tabmix.onemen, Unassigned, NeedInfo)
References
(Regression)
Details
(Keywords: regression)
(In reply to :Gijs from bug 1819675 - comment #40)
All I want Is to point for inconsistency between reopening last closed tab/s with shortcut ctrl-shift-t/cmd-shift-t
and the visibility of closed tabs in Recently Closed Tabs
.
When window A have no closed tabs, but Window B have closed tabs, in both window Recently Closed Tabs
will show closed tabs from window B.
but using ctrl-shift-t/cmd-shift-t
in Window A will do nothing.
- clear all recent history in window A (so previous session's tabs aren't in closed tabs)
- open new window B
- open example.com in window B
- open
about:config
in window B - close example.com
Now both window A
and window B
have one closed tab visible in Recently Closed Tabs
6. ctrl-shift-t/cmd-shift-t
- in window A
will do nothing.
7. ctrl-shift-t/cmd-shift-t
- in window B
will do nothing reopen last closed tab.
I find this behavior to be unexpected.
I expects that when browser.sessionstore.closedTabsFromAllWindows
is on ctrl-shift-t/cmd-shift-t
will undo the last close action in the current session.
lets continue...
8. Now we don't have any closed tabs and Recently Closed Tabs
is grayed out in both windows.
9. In window B, close example.com, (window B still have about:config
, both windows have Recently Closed Tabs
visible)
10. closed window B. (window A, have Recently Closed Tabs
and Recently Closed Windows
enabled)
11. ctrl-shift-t/cmd-shift-t
in window A
will restore window B
.
In summery, there is different behavior for ctrl-shift-t/cmd-shift-t
in window A, in step 6 and step 11.
Comment 1•17 days ago
|
||
:peterv, since you are the author of the regressor, bug 181967, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•17 days ago
|
Comment 2•17 days ago
|
||
Set release status flags based on info from the regressing bug 1819675
Comment 3•17 days ago
|
||
Thanks for filing! I'll leave the session store folks to further triage this.
Description
•