Closed
Bug 1954341
Opened 1 month ago
Closed 28 days ago
Tab group briefly uncollapsed at original position when dragged to start/end of tab bar
Categories
(Firefox :: Tabbed Browser, defect, P1)
Firefox
Tabbed Browser
Tracking
()
VERIFIED
FIXED
138 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox136 | --- | unaffected |
firefox137 | --- | unaffected |
firefox138 | --- | verified |
People
(Reporter: tabmix.onemen, Assigned: dao)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-tabgrps-dnd])
Attachments
(1 file)
When dropping group, by dragging it label, before first tab or after last tab, the group un-collpased in its old place for a split second before it moves to its new position.
tested on latest Nightly with clean profile
Preparation:
- open multiple tabs
- create group, make sure to have more non grouped tabs
- move the group by dragging its label
Drag:
- group is collapsed while dragging as expected
Drop:
- when the drop position is start/end of tab bar, the group is visible again in its original position for a split second before it moves to its new position.
- when the drop position is other then start/end of tab bar the group immediately appears in its new position.
Comment 1•1 month ago
|
||
:dao, since you are the author of the regressor, bug 1908439, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Flags: needinfo?(dao+bmo)
Assignee | ||
Updated•1 month ago
|
Severity: -- → S3
Points: --- → 2
Flags: needinfo?(dao+bmo)
Priority: -- → P1
Whiteboard: [fidefe-tabgrps-dnd]
Updated•1 month ago
|
Assignee | ||
Updated•1 month ago
|
Assignee: nobody → dao+bmo
Assignee | ||
Comment 2•1 month ago
|
||
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4c75c7be8565
Disable tabdrop-samewindow transition for dragged tab groups. r=sthompson,tabbrowser-reviewers
Comment 4•28 days ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 28 days ago
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
Comment 5•26 days ago
|
||
Verified as fixed in our latest Nightly 138.0a1 (2025-03-26)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•