Closed
Bug 1479468
Opened 6 years ago
Closed 6 years ago
Seek bar loses functionality while being dragged at the beginning or at the end of the progress chart
Categories
(DevTools :: Inspector: Animations, defect, P3)
Tracking
(firefox62 wontfix, firefox63 verified)
VERIFIED
FIXED
Firefox 63
People
(Reporter: vlucaci, Assigned: daisuke)
Details
Attachments
(2 files)
Seek Bar losing functionality.gif
[Affected versions]: -62.0b12 [Affected platforms]: -all supported [Steps to reproduce]: 1.Go to https://rawgit.com/dadaa/3b73f847427025b51ba1ab7333013d0c/raw/77f3f0bb884875a179c3407f73bf8a8dd54751c9/doc_simple_animation.html 2.Open Animation Inspector 3.Choose the <body> or a <div> element. 4.Click on the seek bar and with the mouse button pressed go either to the beginning or at the end of the animation. [Expected result]: -Dragging the seek bar either at the beginning or at the end of the animation should not render the seek bar to lose its functionality. [Actual result]: -Dragging the seek bar either at the beginning or at the end of the animation will render the seek bar to remain stuck in these 2 positions. [Regression range]: - This issue is not a regression. [Additional notes]: - This issue occurs with a higher repro rate when moving the mouse cursor outside of the animation progress bar.
|
Assignee | |
Updated•6 years ago
|
Priority: -- → P3
|
|
Assignee | |
Comment 1•6 years ago
|
||
|
|
Assignee | |
Comment 2•6 years ago
|
||
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=c0e4155ffe7478c9b4675182c773bf1f39ff44ef
Assignee: nobody → dakatsuka
|
||
Comment 3•6 years ago
|
||
Comment on attachment 9000151 [details] Bug 1479468: Change mouse target to ownerGlobal.top and remove mouse out event. r=gl Gabriel [:gl] (ΦωΦ) has approved the revision.
Attachment #9000151 -
Flags: review+
Pushed by dakatsuka@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0c0495028107 Change mouse target to ownerGlobal.top and remove mouse out event. r=gl
|
||
Comment 5•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/0c0495028107
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
|
||
Comment 6•6 years ago
|
||
Given that we're only a couple weeks away from shipping 63 and this doesn't appear to be a new issue, I think this can ride the trains. Feel free to nominate for Beta approval if you feel strongly otherwise, however.
|
||
Updated•6 years ago
|
Flags: qe-verify+
|
||
Comment 7•6 years ago
|
||
Reproduced with 63.0a1 (2018-07-18) Verified on 63.0b8 and 64.0a1 for win10x64, mac10.13.6, Ubuntu16.04. Can confirm that the issue is no longer reproducible.
You need to log in
before you can comment on or make changes to this bug.
Description
•