LGTM3 On Wed, Sep 6, 2023 at 8:44 AM Alex Russell <slightly...@chromium.org> wrote:
> Sorry for the slow reply. I agree that Stefan's post is great, but I'm not > sure it's what we'd like to see in terms of design-time process here. In > general, we want to see features built with developer involvement, which is > why Explainers and Incubation are important. Post-hoc documentation is > helpful, but not a replacement for showing our work and discussing > potential design alternatives with end-users. Given that we're not going > first here, I'm not going to block here, but for future work, know that > this isn't the bar and isn't how our process works. > > On TAG review, as Yoav says, please send an FYI so that when we do the > next feature, the folks there have this context. Our process doesn't allow > us to skip this. > > Best, > > Alex > > On Wednesday, September 6, 2023 at 8:17:47 AM UTC-7 Yoav Weiss wrote: > >> LGTM2 >> >> On Thu, Aug 31, 2023 at 2:41 PM 'Aaron Krajeski' via blink-dev < >> blink-dev@chromium.org> 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 <slightly...@chromium.org> >>> 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 arg...@chromium.org 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 < >>>>> r...@igalia.com> 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 blink-dev+unsubscr...@chromium.org. >>> 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 blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/aa23cec1-5edd-42e8-aeca-e2f0742a5107n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/aa23cec1-5edd-42e8-aeca-e2f0742a5107n%40chromium.org?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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-nVVyG0iAzOL-mQTLDZDnSoGBdQjDdLd2rNWhLAVNoBA%40mail.gmail.com.
