Re: [csswg-drafts] [web-animations-2][css-animations-2] What to do with keyframe offsets outside of animations. (#7825)

I suppose we expected developers to omit `animation-delay` from the corresponding declarations altogether, right?

Then what would be the expected behavior for `@keyframes` offsets that _are_ "contained" within the declared `animation-delay`? E.g:

```css
@keyframes fade-in-animation {
  contain 0% { opacity: 0; }
  contain 100% { opacity: 1; }
}
.elem {
  animation: fade-in-animation;
  animation-timeline: view-timeline;
  animation-delay: enter 50% exit 50%;
}
```

Does the `animation-delay` here overrides the offsets? Vice versa?
Isn't having both problematic regardless of the values?
If so, then is it really worth the trouble to try and fix it?

I don't think I'd expect neither clamping nor mapping the values of one to the other.
Perhaps a more expected behavior would be that of a cascading nature, meaning, that one overrides the other. Because I also don't see how allowing both can provide any more value to the author.

-- 
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7825#issuecomment-1268973258 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 5 October 2022 21:03:38 UTC