Closed
Bug 1944416
Opened 1 month ago
Closed 1 month ago
Individual tabs from closed tab groups in closed windows cannot be restored from history menus
Categories
(Firefox :: Session Restore, defect, P1)
Firefox
Session Restore
Tracking
()
VERIFIED
FIXED
137 Branch
Tracking | Status | |
---|---|---|
firefox137 | --- | verified |
People
(Reporter: jswinarton, Assigned: jswinarton)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
(Whiteboard: [fidefe-tabgrps-sessionstore] )
Attachments
(1 file)
Steps to reproduce:
- Open some "worth-saving" (i.e. not
about:blank
tabs). Put some (but not all — see bug1941622) into a tab group. - Right click the tab group label and click "delete tab group".
- Open a new window.
- Close the original window.
- From the top menu, go to "History > Recently Closed Tabs". Find the closed tab group in the list. Click any of the tabs within that tab group.
Expected result:
The tab opens in the new window.
Actual result:
Nothing happens.
This is a follow-on bug from bug1932941, which allows users to reopen closed tab groups from closed windows, but not individual tabs within the tab group.
Assignee | ||
Updated•1 month ago
|
Blocks: 1907100
Severity: -- → S3
Points: --- → 2
Priority: -- → P2
Whiteboard: [fidefe-tabgrps-sessionstore]
Updated•1 month ago
|
Updated•1 month ago
|
Priority: P2 → P1
Assignee | ||
Comment 1•1 month ago
|
||
Updated•1 month ago
|
Assignee: nobody → jswinarton
Status: NEW → ASSIGNED
Pushed by jswinarton@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/053595a05e65
Restore individual tabs from closed groups in closed windows r=dao,sessionstore-reviewers
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
Updated•7 days ago
|
Flags: qe-verify+
Comment 4•13 hours ago
|
||
Reproduced the issue with Firefox 136.0a1 (2025-01-28) on macOS 14.
The issue is verified fixed with Firefox 138.0a1 (20250310205849) and Firefox 137.0b4 (20250310091737) on macOS 14, Windows 10 and Ubuntu 22.
You need to log in
before you can comment on or make changes to this bug.
Description
•