Closed
Bug 1473293
Opened 7 years ago
Closed 7 years ago
<div> element looses information after setting custom animation playback rate for animation bar
Categories
(DevTools :: Inspector: Animations, defect)
Tracking
(firefox61 unaffected, firefox62 affected, firefox63 affected)
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox61 | --- | unaffected |
| firefox62 | --- | affected |
| firefox63 | --- | affected |
People
(Reporter: vlucaci, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
|
1.61 MB,
image/gif
|
Details |
div nothing to display.gif
[Affected versions]:
- 62.0b5
- 62.0b4
[Affected platforms]:
- Windows 10x64
- macOS 10.13
- Ubuntu 16.04x64
[Steps to reproduce]:
1. Launch Firefox
2. Enable the new animation inspector (go to about:config and set devtools.new-animationinspector.enabled to true, then restart the browser)
3. Open the following animation https://rawgit.com/dadaa/3b73f847427025b51ba1ab7333013d0c/raw/77f3f0bb884875a179c3407f73bf8a8dd54751c9/doc_custom_playback_rate.html
4. Open the Inspector and select the Animations tab from the right pane.
5. Click on <body> and select 0.1x animation speed.
6. Select the first <div> and change the speed to 10x.
7. Go through both <div> elements multiple times.
[Expected result]:
- The animation's scale, graph and counter are successfully displayed each time a <div> element is selected.
[Actual result]:
- After switching between <div> elements multiple times the "No animations ere found for the current element. Pick another element from the page." message is displayed instead for either one of the <div> elements
[Regression range]:
-Will return with a regression range ASAP.
[Additional notes]:
- No errors are displayed inside the Web Console.
|
||
Comment 1•7 years ago
|
||
I don't think, this is a bug.
The reason why we got "No animations are found for the current element" message was because the first animation was finished already, I guess.
Could you confirm again?
|
Reporter | |
Comment 2•7 years ago
|
||
(In reply to Daisuke Akatsuka (:daisuke) from comment #1)
> I don't think, this is a bug.
> The reason why we got "No animations are found for the current element"
> message was because the first animation was finished already, I guess.
> Could you confirm again?
I have retried keeping your comment in mind and it seems that you are correct. Once the animation has finished the loop, the "No animations are found for the current element".
|
|
||
Comment 3•7 years ago
|
||
Thank you for confirming!
Please let me close this bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•