Closed
Bug 1944844
Opened 27 days ago
Closed 27 days ago
Tab groups are not created with Drag and Drop when Tab group indicators are displayed
Categories
(Firefox :: Tabbed Browser, defect, P1)
Tracking
()
VERIFIED
FIXED
136 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | --- | verified |
People
(Reporter: rdoghi, Assigned: dao)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-tabgrps-dnd])
Attachments
(2 files)
Found in
- 136.0a1 (2025-01-30) ID 20250130092924
Affected versions
- 136.0a1 (2025-01-30) ID 20250130092924
Affected platforms
- all
Steps to reproduce
- Drag a Tab over a 2nd Tab and Release it when they both show a blue border.
Expected result
- As soon as the Tabs show a Blue border it should create the Tab group.
Actual result
- Users have to keep one Tab over the other for a longer period of time in order to create the Tab group.
Regression range
4:04.67 INFO: Last good revision: 2b7278af32c77e822c8cc5dad005e033c08bfd3b
4:04.67 INFO: First bad revision: f8fda1ba5cd3ee4d27e6e337803cdf53eaad9011
4:04.68 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2b7278af32c77e822c8cc5dad005e033c08bfd3b&tochange=f8fda1ba5cd3ee4d27e6e337803cdf53eaad9011
Flags: needinfo?(dao+bmo)
Assignee | ||
Updated•27 days ago
|
Severity: -- → S3
Points: --- → 1
Flags: needinfo?(dao+bmo)
Priority: -- → P1
Whiteboard: [fidefe-tabgrps-dnd]
Updated•27 days ago
|
Assignee | ||
Comment 1•27 days ago
|
||
Updated•27 days ago
|
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/581e4f9d91fd
Set dropElement before returning early. r=tabbrowser-reviewers,dwalker
Comment 3•27 days ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 27 days ago
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
Updated•27 days ago
|
Reporter | ||
Comment 4•27 days ago
|
||
This issue is Verified as fixed in our latest Nightly build 136.0a1 (2025-01-30)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•