Closed
Bug 1945118
Opened 26 days ago
Closed 26 days ago
Sometimes tabs cannot be moved to a new position
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
VERIFIED
FIXED
136 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | --- | verified |
People
(Reporter: atrif, Assigned: dao)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-tabgrps-dnd])
Attachments
(3 files)
Found in
- 136.0a1 (2025-01-31)
Affected versions
- 136.0a1 (2025-01-31)
Tested platforms
- Affected platforms: Windows 10x64, macOS 12, Ubuntu 24
- Unaffected platforms: none
Steps to reproduce
- Open the uploaded profile (link) and move the middle tab to the right.
Expected result
- The tab is moved.
Actual result
- The tab is not moved.
Regression range
Additional notes
- Attached a screen recording.
Reporter | ||
Comment 1•26 days ago
|
||
Hello Dao! It seems that mozregression points at bug 1944844. Can you please have a look? Thank you!
Flags: needinfo?(dao+bmo)
Reporter | ||
Comment 2•26 days ago
|
||
Sorry for the spam. It seems that this can be easily reproduced on a new profile just by dragging the first tab after the second one.
Assignee | ||
Updated•26 days ago
|
Updated•26 days ago
|
Assignee | ||
Comment 3•26 days ago
|
||
Updated•26 days ago
|
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b862eba09e7a
Revert change from bug 1944844 and fix differently, by having #triggerDragOverCreateGroup update dragData. r=dwalker,jswinarton,tabbrowser-reviewers
Pushed by sstanca@mozilla.com:
https://hg.mozilla.org/mozilla-central/rev/ca3ce1c36b37
Revert change from bug 1944844 and fix differently, by having #triggerDragOverCreateGroup update dragData. r=dwalker,jswinarton,tabbrowser-reviewers
Comment 6•26 days ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 26 days ago
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
Comment 7•26 days ago
|
||
This issue is Verified as fixed in our latest Nightly Build 136.0a1 (2025-01-31)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•