[csswg-drafts] [css-animations] Handling values where endpoints are valid, but midpoints are IACVT (#10369)

tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-animations] Handling values where endpoints are valid, but midpoints are IACVT ==
In #10220 we have a situation where the two endpoints of a `width` interpolation, say, might be large-but-valid `calc-size()` functions, but the interpolation midpoints are invalid due to the calculation getting too large. I'm handling that "too large" case by saying the property becomes invalid-at-computed-value-time, since it's essentially the same issue as variable substitution, [which can also become too large via billion-laugh attacks](https://drafts.csswg.org/css-variables/#long-variables).

This produces a new case that was previously not possible in animations, where two values are valid to interpolate, but their mid-interpolation value isn't valid. In Chrome's implementation, @dbaron isn't sure how to even handle that, and is currently instead doing something simpler.

How *should* we handle this? I'm inclined to say that the animation should fall back to discrete in this case, since the two endpoints are, by definition, valid.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10369 using your GitHub account


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

Received on Friday, 24 May 2024 22:39:26 UTC