Closed
Bug 1095916
Opened 10 years ago
Closed 10 years ago
CSS animation resets when animation and transition are animating the same property and a style change happens
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: sombra2eternity, Assigned: dbaron)
References
Details
Attachments
(1 file)
(deleted),
text/html
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141013200257
Steps to reproduce:
http://jsfiddle.net/sombra2eternity/qmb2qhz4/2/
I declared a css animation while increment parent top position via javascript.
Actual results:
The animation make jumps randomly
Expected results:
The parachute cat should move down smooth.
Webkit produces expected results.
Updated•10 years ago
|
Component: Untriaged → Layout
OS: Linux → All
Product: Firefox → Core
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 33 Branch → Trunk
Updated•10 years ago
|
Component: Layout → CSS Parsing and Computation
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
This is related to having an animation and a transition on the same property. The 'transition' line is unneeded and removing that fixes it. (And there's no -webkit-transition line, so if you actually need the webkit prefixes, then that might make a difference.
We should retest after bug 960465 lands.
Depends on: 960465
Hardware: x86_64 → All
Summary: Css animation keyframe get reset when javascript styles applied → CSS animation resets when animation and transition are animating the same property and a style change happens
Assignee | ||
Comment 3•10 years ago
|
||
Fixed by bug 960465 (or, very unlikely, something else that landed the same day).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → dbaron
Updated•10 years ago
|
QA Whiteboard: [good first verify]
You need to log in
before you can comment on or make changes to this bug.
Description
•