Closed
Bug 1946339
Opened 21 days ago
Closed 2 days ago
Dragged tab misplaced by one position when dropping after grouping indicator disappears
Categories
(Firefox :: Tabbed Browser, defect, P2)
Tracking
()
VERIFIED
FIXED
137 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | --- | disabled |
firefox137 | --- | verified |
People
(Reporter: ke5trel, Assigned: dao)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-tabgrps-dnd])
Attachments
(2 files)
STR:
- Drag a tab and move it multiple positions away on latest Nightly 137.0a1 (2025-02-05) with
browser.tabs.groups.enabled = true
. - Before dropping, make sure the grouping indicator appears and then slowly move until it disappears.
- Drop the tab.
Expected:
Drops in current location.
Actual:
Drops offset one position away.
Not fixed by Bug 1945118.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2361e3eb1d64e007b626427992edfbf5662214b5&tochange=581e4f9d91fd7af32f4f65d2673f23acab9df927
Regressed by Bug 1944844.
Comment 1•21 days ago
|
||
:dao, since you are the author of the regressor, bug 1944844, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Flags: needinfo?(dao+bmo)
Updated•20 days ago
|
Assignee | ||
Updated•20 days ago
|
Blocks: 1907101
Severity: -- → S3
Flags: needinfo?(dao+bmo)
Priority: -- → P2
Whiteboard: [fidefe-tabgrps-dnd]
Updated•20 days ago
|
Assignee | ||
Updated•2 days ago
|
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Assignee | ||
Updated•2 days ago
|
Assignee | ||
Comment 2•2 days ago
|
||
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3790755d3b4c
Fix stability of group creation indicator. r=jswinarton,tabbrowser-reviewers
Comment 4•2 days ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 days ago
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
Comment 5•2 days ago
|
||
Verified as fixed in our latest Nightly 137.0a1 (2025-02-25)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•