- From: Steinar H. Gunderson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Nov 2024 09:47:46 +0000
- To: public-css-archive@w3.org
sesse has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-easing] Resolving curves not available at parse time == https://drafts.csswg.org/css-easing/#funcdef-linear specifies: “If an argument lacks a [<percentage>](https://drafts.csswg.org/css-values-4/#percentage-value), its [input progress value](https://drafts.csswg.org/css-easing/#easing-function-input-progress-value) is initially empty, but that is immediately corrected by [linear() canonicalization](https://drafts.csswg.org/css-easing/#linear-canonicalization) after parsing.” However, it is not always possible to canonicalize at parse time. For instance, if any of the stops' x values is `calc(0.5 + 0.2 * sign(1em - 1px))`, we may need to wait until the style is computed before we know if it needs to be clamped to the previous point or not. How do we handle this? What if _some_ of the stops may be resolvable but not all of them? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11211 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 November 2024 09:47:47 UTC