Re: [csswg-drafts] [css-easing] Resolving curves not available at parse time (#11211)

The CSS Working Group just discussed `[css-easing] Resolving curves not available at parse time`, and agreed to the following:

* `RESOLVED: Copy linear gradients timing details into the linear function`

<details><summary>The full IRC log of that discussion</summary>
&lt;JoshT> TabAtkins: Spec text for linear easing function has canonical ???<br>
&lt;JoshT> ... steps for filling in steps that have empty inputs like gradients<br>
&lt;astearns> s/canonical/canonicalization/<br>
&lt;dholbert> s/canonical ???/canonicalization/ (I think)<br>
&lt;JoshT> ... but it lacks the timing details that linear gradients put in for values that can't be resolved until computed value time<br>
&lt;JoshT> ... spec bug? I recommend we copy details from linear gradients because it's close to a colour stop list<br>
&lt;JoshT> weinig: can we abstract it into something more general?<br>
&lt;JoshT> TabAtkins: my policy is to wait for a third thing? but I'll see if it makes sense<br>
&lt;TabAtkins> WET code - write everything thrice<br>
&lt;JoshT> weinig: when I implemented this in WebKit, did at computed value time, but i don't expect this to be a compat issue<br>
&lt;JoshT> TabAtkins: proposed resolution is to copy linear gradients into the ??? function<br>
&lt;JoshT> RESOLVED: Copy linear gradients timing details into the linear function<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11211#issuecomment-2842523956 using your GitHub account


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

Received on Wednesday, 30 April 2025 16:14:05 UTC