Re: [csswg-drafts] [css-animations] Resolving dependencies in keyframes (#5125)

Thank you @birtles! This means that current state of affairs is that G-β is supposed to be the correct behavior? If I'm not mistaken, this is approximately the same as option 3 here. (Right?)

> I really tried hard to preserve specified values in the CSS animation keyframes from getKeyframes() but it proved impossible and when I spoke with @graouts and @flackr they agreed we should just use the computed values.

But "just" using computed values doesn't work either, does it?

Say there's an animation:

```
@keyframes test {
  from { width: 1em; }
  to { width: 2em; }
}
```
And at the same time, there's a transition on `font-size` that moves from `10px` to `20px` in the same time period. The computed value of `font-size` is then determined by the value the transition adds to the cascade. Is the idea that getKeyframes should return (an object equivalent to):

```
@keyframes test {
  from { width: 10px; }
  to { width: 40px; }
}
```

Because, at the time getKeyframes is called (and at any other time really), there is only _one_ computed value for `font-size`. The `em` unit can't resolve to different things (currently, without new concepts).

If the above is what we want, then we're not substituting "the" computed value, but some value that's equal to the would-be computed value at the time indicated by the keyframe.

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

Received on Friday, 29 May 2020 10:44:00 UTC