Closed Bug 1957434 Opened 1 year ago Closed 1 year ago

Dragging tab to the end of the tab strip briefly animates it from the original position when dropping

Categories

(Firefox :: Tabbed Browser, defect, P1)

Firefox 138
defect
Points:
1

Tracking

()

VERIFIED FIXED
139 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox137 --- unaffected
firefox138 --- verified
firefox139 --- verified

People

(Reporter: ke5trel, Assigned: dao)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression, Whiteboard: [fidefe-tabgrps-dnd])

Attachments

(3 files)

STR:

  1. Drag a tab frome one end of the tab strip to the other.
  2. Keep dragging so that it hits hard against the end of the strip.
  3. Drop the tab.

Expected:
Tab remains in the final end position.

Actual:
Tab briefly returns to original position before animating to final end position.

Does not happen when dropping just before tab hits end of strip.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=653a7b21210b5b61a36af11b99ccd51e6c85a905&tochange=aa8a29bd1fb9668c81475b534b4ceb220dd4fe55

Regressed by Bug 1955112.

:dao, since you are the author of the regressor, bug 1955112, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(dao+bmo)
Blocks: 1907101
Severity: -- → S2
Points: --- → 3
Flags: needinfo?(dao+bmo)
Priority: -- → P1
Whiteboard: [fidefe-tabgrps-dnd]
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED

I expect that bug 1955112 was really a duplicate of bug 1954163. Based on that, let's remove this workaround since it's causing trouble.

Points: 3 → 1
Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6ecfc5bd189e Remove workaround for bug 1954163. r=dwalker,tabbrowser-reviewers
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch

The patch landed in nightly and beta is affected.
:dao, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox138 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(dao+bmo)
Flags: needinfo?(dao+bmo) → qe-verify+

Verified as fixed in our latest Nightly 139.0a1 (2025-04-08)

I expect that bug 1955112 was really a duplicate of bug 1954163. Based on that, let's remove this workaround since it's causing trouble.

Attachment #9477784 - Flags: approval-mozilla-beta?

beta Uplift Approval Request

  • User impact if declined: Please see https://bugzilla.mozilla.org/show_bug.cgi?id=1957434#c0
  • Code covered by automated testing: no
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: -
  • Risk associated with taking this patch: low
  • Explanation of risk level: we have no evidence that bug 1955112 was still an issue after bug 1954163 landed
  • String changes made/needed: none
  • Is Android affected?: no
Attachment #9477784 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [qa-triaged]

Verified as fixed in our latest Beta 138.0b5

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triaged]
Flags: qe-verify+
Regressions: 1967177
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: