Re: [csswg-drafts] [css-easing] Should we include the infinity for output progress value? (#8344)

You still can't get a NaN.  If you try and write either into the syntax, like `linear(0, calc(infinity) 100%)`, it'll clamp to a UA-specified large value once the infinity escapes the `calc()`; similar with NaN (censored into an infinity, then clamped).

And you can't get a NaN in the output, either - none of the functions allows that to happen. Both linear() and cubic-bezier() have matching discontinuous behavior if the extrapolation line would *actually* be vertical, instead treating the first/last point as giving a constant output value.

You *can* potentially get an infinity, if you use a sufficiently sloped function and a sufficiently large/small input outside of the 0-1 range, but that should ideally be clamped as well, since it's an artifact of translating it to a JS double. So that should occur at the WebAnimations side, I think. I can put a note in Easing about it, tho.

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


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

Received on Thursday, 12 September 2024 20:53:54 UTC