On Mon, Jan 27, 2025 at 3:08 AM Noam Rosenthal <nrosent...@chromium.org> wrote:
> On Mon, Jan 27, 2025 at 2:56 AM Domenic Denicola <dome...@chromium.org> > wrote: > >> This overall seems promising, but a few inline comments. The only >> blocking one is the question about open spec edits. >> >> On Thursday, January 23, 2025 at 4:42:34 AM UTC+9 Chromestatus wrote: >> > ... > Anticipated spec changes >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> None >> >> >> https://github.com/w3c/csswg-drafts/labels/css-shapes-2 has quite a lot >> of open issues. Several of them relate to shape(), I believe: >> > ... > >> - https://github.com/w3c/csswg-drafts/issues/10647 >> >> This one is not actionable and doesn't affect shape(), it's about path(). > I think "not actionable <https://www.merriam-webster.com/dictionary/actionable>" isn't a great way to describe this issue: Lea's suggesting that this functionality be provided as part of the `path()` function and that `shape()` not be defined at this time. That's a concrete action that affects `shape()`. Jeffrey -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANh-dXnfdH3fGN172vKyMhwoAdTnQHxc0MDjD7UUy3vmzNbhJA%40mail.gmail.com.
