The PR has been merged into the WebGL spec, viewable at https://registry.khronos.org/webgl/specs/latest/1.0/ . Are OWNERS here comfortable taking that as a positive signal from Mozilla/Apple?
On Wed, Dec 20, 2023 at 11:27 AM Ken Russell <k...@chromium.org> wrote: > (Re-sending from correct email address) > > > On Wed, Dec 20, 2023 at 8:37 AM Chris Harrelson <chris...@chromium.org> > wrote: > >> >> >> On Mon, Nov 27, 2023 at 1:20 PM 'Christopher Cameron' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Contact emailsccame...@chromium.org >>> >>> ExplainerNone >>> >>> Specificationhttps://github.com/KhronosGroup/WebGL/pull/3222 >>> >>> Summary >>> >>> WebGL allows rendering into textures and renderbuffers of many different >>> pixel formats (e.g, 8-bit, floating-point, sRGB-encoded, etc). The drawing >>> buffer of WebGL (the buffer that is passed to the compositor) is 8-bit by >>> default. This feature allows WebGL to configure the pixel format of this >>> drawing buffer. This feature enables WebGL developers to: * avoiding an an >>> extra copy convert their rendering to the default drawing buffer pixel >>> format * draw content that has a more than 8 bits of precision The latter >>> feature unlocks several additional applications * very wide color gamut >>> content without loss of precision * medical applications which require >8 >>> bits of precision * high dynamic range applications (when available) >>> >>> >>> Blink componentBlink>WebGL >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebGL> >>> >>> TAG reviewNone >>> >>> TAG review statusNot applicable >>> >>> Risks >>> >>> >>> Interoperability and Compatibility >>> >>> None. >>> >>> >>> *Gecko*: Positive Feature authored by Mozilla. >>> >> >> If they didn't tell you specifically that it's not necessary, please file >> one, thanks. >> > > FYI Mozilla's rep (and author of the drawingBufferStorage spec) gave a > thumbs-up on Khronos' private WebGL working group mailing list. I'll work > to get https://github.com/KhronosGroup/WebGL/pull/3222 landed; I think > that should suffice as signal from Mozilla as well as other vendors. > > -Ken > > > >> >> >>> >>> *WebKit*: No signal ( >>> https://github.com/WebKit/standards-positions/issues/278) >>> >>> *Web developers*: Positive Positive feedback from several high profile >>> web developers - 3D engines that use physically based rendering - image >>> editing formats (especially for HDR) - medical imaging applications (which >>> require >8 bit precision) >>> >>> *Other signals*: This feature's specification was authored by Mozilla. >>> >>> Ergonomics >>> >>> None. >>> >>> >>> Activation >>> >>> No. >>> >>> >>> Security >>> >>> None. >>> >>> >>> WebView application risks >>> >>> Does this intent deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>> None >>> >>> >>> Debuggability >>> >>> No additional debugging support should be needed. >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)?Yes >>> >>> The underlying technology (floating point textures) has almost universal >>> support. >>> >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ?No >>> >>> This feature is fully tested using WebGL conformance tests, which has >>> been checked in. >>> >>> >>> Flag name on chrome://flags >>> >>> Finch feature nameNone >>> >>> Requires code in //chrome?False >>> >>> Availability expectationFeature is available on Web Platform in less >>> than a year following launch in Chrome. >>> >>> Adoption expectationSeveral specific partners have been using this >>> feature being chrome://flags' "experimental web platform features", and >>> intend to adopt this as soon as it is supported. >>> >>> Estimated milestones >>> Shipping on desktop 122 >>> Shipping on Android 122 >>> Shipping on WebView 122 >>> >>> 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 >>> >>> Link to entry on the Chrome Platform Status >>> https://chromestatus.com/feature/5146687245123584 >>> >>> Links to previous Intent discussionsIntent to prototype: >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj-HFt%3Dk5NBHb5SyNT0ERn6w13S3U8%3DBjV8-4EB4EUoAkw%40mail.gmail.com >>> >>> -- >>> 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/CAGnfxj-0wf-RFAnEaKjT3kJPrMo78QCaEhQZ5EXua4sg2O9qKg%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj-0wf-RFAnEaKjT3kJPrMo78QCaEhQZ5EXua4sg2O9qKg%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/CAMYvS2dyA0p4zUykxus8u%3DoHV_4CcJEj4NqR4aGyBMZ7g2HPtw%40mail.gmail.com.
