- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Jan 2025 16:43:12 +0000
- To: public-css-archive@w3.org
> I think the shape syntax fulfills many of the issues raised in [#9889](https://github.com/w3c/csswg-drafts/issues/9889), but maybe not all of them. I'd like to see a list of potential features of a separate `shape` function that are currently not supported, so we can judge whether it's worth saving `shape()` for a different thing in future. We can also have potential `shape()` overloads in the future. But I don't think that means that the current `shape()` proposal should be a `path()` overload. `shape()` is a set of commands that are a recipe to generating a path given a context (e.g. custom CSS properties, the reference box). If we can maintain these definitions, we can expand both in different directions using overloads. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10647#issuecomment-2619528640 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 January 2025 16:43:13 UTC