Closed
Bug 1940791
Opened 2 months ago
Closed 2 months ago
When opening a tab group from the tab overflow menu, it should become the active group
Categories
(Firefox :: Session Restore, defect)
Firefox
Session Restore
Tracking
()
VERIFIED
FIXED
136 Branch
Tracking | Status | |
---|---|---|
firefox136 | --- | verified |
People
(Reporter: amylee, Assigned: dao)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-tabgrps-sessionstore][UX-tabgrps-review])
Attachments
(1 file)
Steps to reproduce [can add screenshots or video recordings for reference]:
- Open many tabs (so it triggers overflow scrolling in the tab strip)
- Create a tab group
- Close and save group
- Reopen group from the TOM menu
Expected behavior [What should have happened?]:
The newly opened group opens in the far right and becomes the active group (with the first tab in the group as the active tab).
Tab group should be visible on the tab strip (moves from overflow to become visible on the tab strip)
Actual behavior [What actually happened?]:
The tab group opens outside of the visible area of the tab strip (far right).
There's no visible feedback that the group is opened (doesn't become the active group with the first tab in group as active tab)
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Blocks: 1908428
Points: --- → 1
Summary: When opening a tab group from the TOM menu, it should become the active group → When opening a tab group from the tab overflow menu, it should become the active group
Whiteboard: [fidefe-tabgrps-tabbrowser] [UX-tabgrps-review] → [fidefe-tabgrps-panels] [UX-tabgrps-review]
Assignee | ||
Updated•2 months ago
|
Component: Tabbed Browser → Session Restore
Whiteboard: [fidefe-tabgrps-panels] [UX-tabgrps-review] → [fidefe-tabgrps-sessionstore][UX-tabgrps-review]
Assignee | ||
Comment 1•2 months ago
|
||
Updated•2 months ago
|
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c37206e5cecb
When restoring a group, select it. r=jswinarton
Comment 3•2 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox136:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
Comment 4•1 month ago
|
||
This issue is verified as fixed in our latest Nightly build 136.0a1 (2025-01-16)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•