Component: Untriaged → Style System (CSS)
Product: Firefox → Core
Could you attach a minimal testcase (html file), please.
Summary: Animations (CSS) not managed singularly → CSS animations execute on display:none elements, so, when display changes later, animation starts in the middle
This version of the testcase is slightly less confusing. The modifications are: * remove prefixes * replace the setInterval with a setTimeout since it only runs once * remove cCount since it's never modified * remove the if (cCount == 1) part since it's never used * add <!DOCTYPE HTML>
Attachment #692723 - Attachment is obsolete: true
This shows that we behave differently when an ancestor of the animating element is display:none (as opposed to the animating element itself being display none).
Oh, really thank you for the explanation, it works fine! So, the animation which is anyway executed in display:none elements, could be considered as a bug? Could it became "optional", maybe through a CSS property as like "-moz-animation-execute-display-none: (true|false)"?
Per comment 4.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Did Bug 960465 change anything here?
OS: Windows 7 → All
Hardware: x86_64 → All
The spec now says: Setting the display property to none will terminate any running animation applied to the element and its descendants. If an element has a display of none, updating display to a value other than none will start all animations applied to the element by the animation-name property, as well as all animations applied to descendants with display other than none. (and has since http://hg.csswg.org/drafts/rev/f661fd2d5fbe )
Though bug 962594 should have fixed this.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 962594
(It's fixed in Firefox 39.)
2 years ago
You need to log in before you can comment on or make changes to this bug.