- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Jul 2024 16:52:38 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-shapes] Clarify which `<basic-shape>` are valid in `shape-*` ``, and agreed to the following: * `RESOLVED: Shapes Level 1 is modified to say that shape-outside takes all <basic-shape>s` * `RESOLVED: Publish a new CRD of Shapes 1 with this change (and whatever else is already in since last publication)` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> smfr: In Shapes 1 the spec says shape-outside accepts only a small list of functions<br> <TabAtkins> smfr: We have new shape functions now - xywh()/etc, shape(), path(), etc<br> <TabAtkins> smfr: Convenient would be to say that <basic-shape> is all such shape functions<br> <TabAtkins> smfr: I think in imp we avoided path() in <basic-shape> at first becuase it was hard to do the geometry to figure out where a line of text hit the boundary<br> <TabAtkins> smfr: But I think we just need to figure it out and make shapes work everywhere<br> <TabAtkins> astearns: Does this need to be in Level 1, or can it go to Level 2?<br> <TabAtkins> smfr: Woudl be a little weird for Level 2 to modify shape-outside here, but it could I guess?<br> <TabAtkins> astearns: No strong opinion eithe rway for me<br> <TabAtkins> astearns: makes sense to me<br> <TabAtkins> +1 from me<br> <TabAtkins> astearns: proposed resolution: Shapes Level 1 is modified to say that shape-outside takes all <basic-shape>s<br> <TabAtkins> RESOLVED: Shapes Level 1 is modified to say that shape-outside takes all <basic-shape>s<br> <TabAtkins> smfr: could i also ask for a new WD?<br> <TabAtkins> smfr: The ED changes the values accepted by circle()/ellipse() grammars too<br> <TabAtkins> astearns: I think this'll be a CRD at this point<br> <TabAtkins> astearns: Which is why I was thinking of putting it in l2, to be lazy<br> <TabAtkins> fantasai: It's not harder to publish a CRD than a WD<br> <TabAtkins> astearns: Do you want a resolution to publish now, or wait for the next issue?<br> <TabAtkins> smfr: next issue is definitely a l2 issue, let's do now<br> <TabAtkins> astearns: so proposed is: Publish a new CRD of Shapes 1 with this change (and whatever else is already in since last publication)<br> <TabAtkins> RESOLVED: Publish a new CRD of Shapes 1 with this change (and whatever else is already in since last publication)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9728#issuecomment-2260954580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 July 2024 16:52:39 UTC