- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 17:06:24 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-shapes-2] In `shape()` It should be possible to specify control points relative to their point on the curve``, and agreed to the following: * `RESOLVED: Add a from-start keyword that goes after the value and latches the coordinate to the beginning of the segment.` <details><summary>The full IRC log of that discussion</summary> <dbaron> noamr: This is about the shape syntax.<br> <dbaron> noamr: Mostly saw ??? a bit complex to define shape syntax with bezier curves, cubic and quadratic.<br> <dbaron> noamr: When we define those curves we first define end points and then control points.<br> <dbaron> noamr: sometimes we want control points relative to start rather than to what we just defined which is the end<br> <dbaron> noamr: this can be boggling<br> <dbaron> noamr: In SVG control points go in order. They always end in the end.<br> <dbaron> noamr: Here we can have either order.<br> <dbaron> noamr: With keyword where you can specify 2 or specify ????<br> <dbaron> noamr: Simon added another issue that I think we should open separately.<br> <dbaron> noamr: Proposal here that I raised that we can discuss is that you can add the word "from" after specify point, can say "From start"<br> <dbaron> noamr: It's getting less and less similar to SVG, for better or for worse.<br> <TabAtkins> q+<br> <dbaron> noamr: Do we want to keep it similar-ish to SVG, with same mental model, or do we want to break free from that.<br> <dbaron> noamr: We were breaking away a bit, but piecemeal.<br> <dbaron> noamr: I think it needs a higher decision about that.<br> <astearns> my vote is to break free if there is good justification<br> <dbaron> noamr: Specifically here because we changed the order of endpoints earlier, it makes it difficult to have points relative to start, and we need another keyword for that.<br> <dbaron> noamr: This becomes quite wordy.<br> <dbaron> noamr: I think with the property syntax, people sometimes avoid it because it adds a lot of CSS.<br> <dbaron> noamr: We need to be careful about not being too verbose.<br> <dbaron> noamr: The SVG ordering allows being a bit more terse.<br> <dbaron> noamr: I think switching the order and allowing using keywords is more verbose.<br> <lea> This issue seems to be related to #10647 (overloading path() for the path syntax that is closer to SVG)<br> <Rossen9> ack TabAtkins<br> <dbaron> I don't have an opinion on exactly ???, but it's complicated... but for the more general case of close to SVG or break free. I don't think we should pay attention to what SVG can do right now. We should continue expanding what's useful regardless of what we can port back to SVG syntax.<br> <ydaniv> +1 to TabAtkins<br> <dbaron> noamr: For now, proposed resolution would be that you can add from keywords that latches the next coordinate to the beginning of the sequence.<br> <dbaron> noamr: you can say from-start, latches the previous coordinate to the start of the segment<br> <dbaron> s/sequence/segment/<br> <TabAtkins> Fine with this for now; I'll review more closely when I get back.<br> <dbaron> RESOLVED: Add a from-start keyword that goes after the value and latches the coordinate to the beginning of the segment.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10667#issuecomment-2379715436 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 September 2024 17:06:25 UTC