I've updated bit.ly/blink-signals to include an exception for Khronos (see the document for details).
Thanks for the developer signal. LGTM1 for this intent! On Wed, May 18, 2022 at 4:19 PM Chris Harrelson <[email protected]> wrote: > > > On Wed, May 18, 2022 at 4:18 PM Chris Harrelson <[email protected]> > wrote: > >> >> >> On Wed, May 18, 2022 at 4:04 PM Ken Russell <[email protected]> wrote: >> >>> On Wed, May 18, 2022 at 3:40 PM Chris Harrelson <[email protected]> >>> wrote: >>> >>>> Hi, comments below. >>>> >>>> On Wed, May 18, 2022 at 11:48 AM Ken Russell <[email protected]> wrote: >>>> >>>>> >>>>>>> On Tue, May 17, 2022 at 3:40 PM 'Christopher Cameron' via blink-dev < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> TAG review status >>>>>>>> N/A. Canvas 2D color managment API already TAG reviewed at >>>>>>>> https://github.com/w3ctag/design-reviews/issues/646 >>>>>>>> >>>>>>> >>>> Should this intent reuse issue 646 then? Are the considerations and API >>>> almost exactly the same as in 2D canvas? Another option is to comment on >>>> that issue describing the WebGL variant of the same feature, and calling >>>> out the notable differences the TAG needs to be aware of to provide useful >>>> feedback. >>>> >>>> >>>>> This specification change was developed in Khronos and followed the >>>>>>>> processes there. >>>>>>>> >>>>>>>> Risks >>>>>>>> >>>>>>>> >>>>>>>> Interoperability and Compatibility >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Gecko: Positive Developed in close collaboration with Mozilla, >>>>>>>> spec changes reviewed by Mozilla. >>>>>>>> >>>>>>>> WebKit: Positive Discussed in ColorWeb CG with WebKit >>>>>>>> representatives >>>>>>>> >>>>>>> >>>> Please file for official signals. Participating in discussions is not >>>> the same as officially supporting. >>>> >>> >>> I'd like to respectfully point out that this API was agreed upon by all >>> major browser implementers in Khronos' WebGL working group, whose processes >>> have been well established over the last decade. The WebGL working group >>> owns the responsibility for evolving this portion of this web API, and the >>> requirement in Blink's processes to fetch signals is causing duplicate work >>> to be done in this context. >>> >>> I would like to respectfully request that Blink's processes be changed >>> to not require implementation signals for WebGL specification changes. Any >>> such changes are already only made with full agreement among Gecko, WebKit >>> and Blink engineers. >>> >> >> Got it, ok. We already have an exception in two cases, let's work >> together on adding it to bit.ly/blink-intents. >> > > ...make that bit.ly/blink-signals. > >> >> >>> >>> >>> Web developers: Strongly positive >>>>>>>> >>>>>>> >>>> Could you give examples of developer support? >>>> >>> >>> Not to speak for Chris Cameron, but this support was requested, with >>> urgency, by Adobe. >>> >>> -Ken >>> >>> -- >>> 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/CAMYvS2dk0%2B1MM8pG6kfLEVQSx_yNEoh6-cF80mmOuv_JenxQeA%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMYvS2dk0%2B1MM8pG6kfLEVQSx_yNEoh6-cF80mmOuv_JenxQeA%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/CAOMQ%2Bw803nEE7J2z%2B2-joguPUzd2wdnqfMBax4ZEK%3D-ChS634Q%40mail.gmail.com.
