Thank you! On Wed, Nov 29, 2023 at 4:24 PM Yoav Weiss <yoavwe...@chromium.org> wrote:
> Thanks! This seems like an important problem to solve.. > > On Monday, November 27, 2023 at 10:20:37 PM UTC+1 Christopher Cameron > wrote: > > Contact emailsccame...@chromium.org > > ExplainerNone > > > A short (inline?) explainer can help reviewers assess what this looks like > and how developers may use it. > > As is, it's not clear what the API surface for this is. > Sure! This adds one new call to the WebGLRenderingContextBase interface (the base interface for WebGL and WebGL2). That call is void drawingBufferStorage(GLenum sizedformat, GLsizei width, GLsizei height); This allows the user to change the pixel format (along with the width and height) of the drawing buffer. This is similar to the existing renderbufferStorage <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.idl;l=601;drc=76de6c12e41b99030fd5413c6f46dabd68862c45> function, which can be used to change these properties of an explicitly allocated offscreen buffer. > > > Specificationhttps://github.com/KhronosGroup/WebGL/pull/3222 > > > What's preventing the PR from landing? > +Ken Russell <k...@google.com> to verify: My understanding is that the PR is to land after there exists an implementation shipping this. > > > > 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. > > *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 milestonesShipping on desktop122Shipping on Android122Shipping > on WebView122 > > 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 Statushttps://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/CAGnfxj9wHToypq6PpVYNajJET0m0RafiBwXPu%2BHG%2BRpQxbpZFw%40mail.gmail.com.
