> Given that this is shipped in Safari, the TAG review is not a blocker based on our process. So I think you can keep it brief.
TAG review is here! https://github.com/w3ctag/design-reviews/issues/894 On Wed, Sep 6, 2023 at 11:17 AM Yoav Weiss <[email protected]> wrote: > LGTM2 > > On Thu, Aug 31, 2023 at 2:41 PM 'Aaron Krajeski' via blink-dev < > [email protected]> wrote: > >> Thanks for your review Alex! >> >> > First, please use the Mozilla Standards Positions process to guage >> their temperature rather than links to bugs: >> >> Chris Lilley opened a bug for that in July, no response yet: >> https://github.com/mozilla/standards-positions/issues/841 >> >> > Next, not having an explainer is not great, and pointing to a >> Google-internal doc is not on. >> >> How about the blog I responded to Rego with, is it sufficient? >> https://www.stefanjudis.com/notes/new-in-css-relative-colors/ >> > > I think Stefan's blog post is a great explainer + it shows developer > enthusiasm towards this! > > >> <https://www.stefanjudis.com/notes/new-in-css-relative-colors/> >> >> > Lastly, please send this feature to the TAG as an FYI. There's no >> "pass" for new, large features like this. >> >> As an issue on github.com/w3ctag/design-reviews/issues? It being an FYI, >> can I keep it brief or do I need to dig around for "User research", "Key >> pieces of existing multi-stakeholder review or discussion of this >> specification" from when the spec was originally written? >> > > Given that this is shipped in Safari, the TAG review is not a blocker > based on our process. So I think you can keep it brief. > > >> >> Thanks! >> Aaron >> >> >> >> >> On Wed, Aug 30, 2023 at 12:25 PM Alex Russell <[email protected]> >> wrote: >> >>> Hey Aaron, thanks for the links. >>> >>> I'm goint to LGTM1 this on the condition you dot some i's and cross some >>> t's. >>> >>> First, please use the Mozilla Standards Positions process to guage their >>> temperature rather than links to bugs: >>> >>> https://mozilla.github.io/standards-positions/ >>> >>> When Mozilla replies, please update the issue and post the reply to this >>> thread. >>> >>> Next, not having an explainer is not great, and pointing to a >>> Google-internal doc is not on. >>> >>> Lastly, please send this feature to the TAG as an FYI. There's no "pass" >>> for new, large features like this. >>> >>> Best, >>> >>> Alex >>> >>> On Wednesday, August 30, 2023 at 8:34:31 AM UTC-7 Aaron Krajeski wrote: >>> >>>> That's not a public link, please could you make it public? >>>> >>>> That's not a great explainer actually (it's my own doc) these are >>>> better: >>>> https://blog.jim-nielsen.com/2021/css-relative-colors/ >>>> https://www.stefanjudis.com/notes/new-in-css-relative-colors/ >>>> >>>> Why no signals from Gecko? Have we filled a standards position request >>>> or do we know other information about Gecko supporting this feature? >>>> >>>> It's part of stable spec right now. Gecko has an implementation bug: >>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1701488 >>>> >>>> I guess some developers have asked about this feature right? Do we have >>>> any info regarding that? >>>> >>>> Yes! Just to name a few: >>>> https://www.matuzo.at/blog/2023/100daysof-day92/ >>>> https://12daysofweb.dev/2022/css-color-spaces-relative-color-syntax/ >>>> https://www.stefanjudis.com/notes/new-in-css-relative-colors/ >>>> https://chriscoyier.net/2023/01/26/relative-color-syntax-plzzzzz/ >>>> "Both *Dave* <https://daverupert.com/2023/01/css-wishlist-2023/> and >>>> *Tyler* <https://cloudfour.com/thinks/tylers-css-wish-list-for-2023/> >>>> pointed >>>> to *the Relative Color Syntax* >>>> <https://www.w3.org/TR/css-color-5/#relative-colors> on their 2023 CSS >>>> Wishlist." >>>> >>>> Thanks to [email protected] for finding these. >>>> >>>> Sorry for the incompleteness of my I2S thread and thank you for the >>>> follow up Rego! >>>> >>>> Cheers, >>>> Aaron >>>> >>>> On Wed, Aug 30, 2023 at 10:54 AM Manuel Rego Casasnovas < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On 29/08/2023 16:17, Aaron Krajeski wrote: >>>>> > *Explainer: *go/rcs-chromium <http://go/rcs-chromium> >>>>> >>>>> That's not a public link, please could you make it public? >>>>> >>>>> > Risks >>>>> > >>>>> > Interoperability and Compatibility >>>>> > >>>>> > None >>>>> > >>>>> > >>>>> > /Gecko/: No signal >>>>> >>>>> Why no signals from Gecko? Have we filled a standards position request >>>>> or do we know other information about Gecko supporting this feature? >>>>> >>>>> > /WebKit/: Shipped (https://caniuse.com/css-relative-colors >>>>> > <https://caniuse.com/css-relative-colors>) >>>>> > >>>>> > /Web developers/: No signals >>>>> >>>>> I guess some developers have asked about this feature right? Do we have >>>>> any info regarding that? >>>>> >>>>> Thanks, >>>>> Rego >>>>> >>>> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPhTwY2hoE4ObOn1zqaWWO8949QGqewJf0VX-etZR0RPskuytA%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPhTwY2hoE4ObOn1zqaWWO8949QGqewJf0VX-etZR0RPskuytA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPhTwY2-YrgBbtdMw7gHZz9cyAEq4V%3DXjKyy9XOU6OWzkKZ-Vw%40mail.gmail.com.
