- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Jan 2024 11:21:33 +0000
- To: public-css-archive@w3.org
> The use case is valid, but I worry a little bit about diverging from SVG polygons (and the regular dictionary definition of “polygon”) for this. Could adding more unit flexibility in path() be an alternative solution? Given the reluctance of browsers to work on SVG, and the fact that there is no SVG WG anymore to evolve SVG further, I think this in practice will end up holding the web platform back 😕 We have also not been tied to SVG capabilities in other places, e.g. we added conic gradients even though SVG does not support them and our gradient syntax is very different (and generally far more usable) than SVG's. We *can* however add this to CSS and then try to get it added to SVG as well. That said, adding more unit flexibility in `path()` is *sorely* needed as well! But it's a separate issue. I can try to spin off something. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9843#issuecomment-1907931874 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 January 2024 11:21:35 UTC