Re: [csswg-drafts] [css-values] "explicitly undefined" (#8865)

No, the issue is that literally *any* numeric result is valid (the whole range from infinity to negative infinity), depending on how close your internal representation is to the asymptote and whether it's slightly smaller or slightly larger. It's inherently untestable without specifying an internal numeric representation, which CSS has intentionally always avoided, to allow impls to use more or less precision, and different types of precision, in various places for optimization reasons.

(You can write tests for this in JS because it's defined in terms of IEEE 64-bit floats.)

Happy to switch over to Infra's term, tho. We use "undefined" or "explicitly undefined" in several places in CSS and have for years, but converging on language is generally good.

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


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

Received on Monday, 22 May 2023 20:57:51 UTC