Handle scroll animations properly when changing animation-timeline from/to none
Categories
(Core :: CSS Transitions and Animations, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox103 | --- | affected |
People
(Reporter: boris, Assigned: boris)
References
(Blocks 2 open bugs, )
Details
Attachments
(1 obsolete file)
It seems we don't handle it well for the case that changing animation-timeline from timeline to none or vice versa. See [1][2]. Need to fix this bug.
| Comment hidden (obsolete) |
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 2•3 years ago
•
|
||
This may be related to web-animations-2: https://drafts.csswg.org/web-animations/#setting-the-timeline.
| Assignee | ||
Comment 3•3 years ago
|
||
Based on Bug 1774060 comment 4, it makes more sense to cancel the CSS animation when changing the animation-timeline to none. And we shouldn't generate the CSS animation if we set animation-timeline: none initially.
| Assignee | ||
Comment 4•3 years ago
|
||
The bug addresses the following cases:
- Set animation-timeline: none initially
-> No CSSAnimation is generated - Set animation-timeline: unknown-timeline initially
-> No CSSAnimation is generated - Change animation-timeline from a scroll-timeline name to none
-> The existing CSSAnimation is cancelled. - Change animation-timeline from a scroll-timeline name to unknown-timeline
-> The existing CSSAnimation is cancelled.
Basically, we treat the null timeline just like what we do for @keyframes.
If there is no matched @keyframes, we don't generate the CSS animation.
Same for timeline.
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 5•3 years ago
|
||
Per the spec comment: https://github.com/w3c/csswg-drafts/issues/7364#issuecomment-1155851858
For now, I'd like to rely on set-the-timeline-of-an-animation procedure to make the decision, so let's close this bug for now.
Updated•3 years ago
|
Description
•