You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps we could define animation to either include <time> values for time-based animations, and have that resolve to animation-delay - which will in turn can be defined as only <time>#; or include only a <timeline-range-name># - and then resolve to animation-range?
Then we could also make these definitions mutually exclusive and also remove the confusion (as discussed in #7901)?
FYI @fantasai@flackr
The text was updated successfully, but these errors were encountered:
Since
animation-duration
has no meaning for scroll-linked animations, as noted here:We could say that
<time>
-related values have no meaning inanimation
shorthand values.Instead, those require an
animation-range
value, also discussed in #7575.Currently,
animation-range
is defined as an alias ofanimation-delay
here: https://drafts.csswg.org/scroll-animations-1/#named-range-animation-declaration.Perhaps we could define
animation
to either include<time>
values for time-based animations, and have that resolve toanimation-delay
- which will in turn can be defined as only<time>#
; or include only a<timeline-range-name>#
- and then resolve toanimation-range
?Then we could also make these definitions mutually exclusive and also remove the confusion (as discussed in #7901)?
FYI @fantasai @flackr
The text was updated successfully, but these errors were encountered: