Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649)

The CSS Working Group just discussed ``[css-shapes-2] `curve to` keyword `using` seems a bit off``, and agreed to the following:

* `RESOLVED: Accept the changes to the shape() grammar`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Summary at https://github.com/w3c/csswg-drafts/issues/10649#issuecomment-2471826022<br>
&lt;TabAtkins> smfr: propsoed syntax for the shape() function<br>
&lt;TabAtkins> smfr: we've talked about this before, it's a tweak<br>
&lt;TabAtkins> smfr: settled on using `with` for the control points. if you specify two control points, separate with a slah.<br>
&lt;TabAtkins> smfr: big addition is using keywords for absolute points, like `curve to top left`, it feels very natural<br>
&lt;TabAtkins> smfr: hline/vline also take those keywords<br>
&lt;TabAtkins> smfr: and new addition, can specify the control points are realtive to the start or end of segment, using "from start" or "from end" syntax<br>
&lt;TabAtkins> smfr: had an open question - arbityrary order of control points and destination points?<br>
&lt;TabAtkins> smfr: so youc ould say `curve ... with ... to...` or `curve ... to ... with ...`<br>
&lt;fantasai> full proposed grammar at https://github.com/w3c/csswg-drafts/issues/10649#issuecomment-2426552611<br>
&lt;TabAtkins> Rossen0: this feels a lot better than the basic shapes syntax before<br>
&lt;fantasai> +1 to the proposal and +1 to allowing reordering<br>
&lt;TabAtkins> +1 to me, I've reviewed all the changes<br>
&lt;noamr7> +1<br>
&lt;TabAtkins> smfr: there's a chunk of wpt already. spec doesn't reflect arbitrary ordering yet, i'll fix that<br>
&lt;TabAtkins> Rossen0: objections?<br>
&lt;TabAtkins> RESOLVED: Accept the changes to the shape() grammar<br>
</details>


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


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

Received on Wednesday, 13 November 2024 17:57:18 UTC