Thanks! It was unclear what the procedure was here since this isn't a new feature, just enabling it on a new platform. I'll make sure they are updated appropriately.
--Brandon On Fri, Oct 27, 2023 at 2:04 PM Chris Harrelson <[email protected]> wrote: > > > On Fri, Oct 27, 2023 at 1:57 PM Mike Taylor <[email protected]> > wrote: > >> LGTM2 % requesting all of the review gates in the chromestatus entry. >> > Ah yes - please do start those reviews. Likely you can mark them as N/A > because this is just shipping an existing API on a new platform. > > >> On 10/27/23 4:25 PM, Chris Harrelson wrote: >> >> LGTM1 - this is an easy one :) >> >> On Fri, Oct 27, 2023 at 1:21 PM 'Brandon Jones' via blink-dev < >> [email protected]> wrote: >> >>> Contact emails [email protected], [email protected] >>> >>> Explainer https://gpuweb.github.io/gpuweb/explainer/ >>> >>> Specification https://www.w3.org/TR/webgpu >>> >>> Design docs >>> https://gpuweb.github.io/gpuweb >>> https://gpuweb.github.io/gpuweb/wgsl >>> https://gpuweb.github.io/gpuweb/explainer >>> >>> Summary >>> This Intent to Ship is specifically for enabling WebGPU by default on >>> Android. WebGPU previously launched on Windows, MacOS, and ChromeOS in >>> M113. See https://chromestatus.com/feature/6213121689518080 for >>> details. >>> >>> WebGPU has been available on Android behind a flag since M111, during >>> which time we have gathered feedback from developers, partners, and >>> Chrome's testing infrastructure to find and address issues on multiple >>> mobile GPU architectures. >>> >>> WebGPU is the successor to the WebGL and WebGL 2 graphics APIs for the >>> Web. It provides modern features such as “GPU compute” as well as lower >>> overhead access to GPU hardware and better, more predictable performance. >>> WebGPU is developed by the “GPU for the Web” W3C community group. >>> >>> >>> Blink component Blink>WebGPU >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebGPU> >>> >>> TAG review https://github.com/w3ctag/design-reviews/issues/626 >>> >>> TAG review status Issues addressed >>> >>> Risks >>> >>> >>> Interoperability and Compatibility >>> >>> With positive signals (and at least WIP implementations) from all >>> browsers and few unresolved issues in the spec repo, the compatibility risk >>> is low and mostly if other implementers find bugs in the spec as they flesh >>> out their WebGPU implementation. >>> >>> >>> *Gecko*: Positive (https://mozilla.github.io/standards-positions/#webgpu >>> ) >>> >>> *WebKit*: In development ( >>> https://github.com/WebKit/WebKit/tree/main/Source/WebGPU/WebGPU) >>> Standards position issue: >>> https://github.com/WebKit/standards-positions/issues/107 >>> >>> *Web developers*: Strongly positive >>> >>> Security >>> >>> See detailed security explainer: >>> https://gpuweb.github.io/gpuweb/#malicious-use >>> >>> >>> 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 >>> >>> Warnings and errors are exposed via dev tools. Specialized tools can be >>> built directly in JavaScript, integrated in applications or as devtools >>> extensions. >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)? No >>> >>> Once enabled on Android, the only Blink platform where WebGPU will not >>> be enabled by default yet is Linux. >>> >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ? Yes >>> >>> The WebGPU Conformance Test Suite is being built at >>> https://github.com/gpuweb/cts and can be integrated as a subdirectory >>> of WPT. It is already integreated into the Chromium CI infrastructure. >>> >>> DevTrial instructions >>> https://github.com/gpuweb/gpuweb/wiki/Implementation-Status#chromium-chrome-edge-etc >>> >>> Flag name on chrome://flags --enable-unsafe-webgpu >>> >>> Finch feature name WebGPUService >>> >>> Requires code in //chrome? False >>> >>> Availability expectation Feature will initially be enabled for Adreno >>> and Mali GPUs (the majority of the mobile market) on Android 12+, with >>> other hardware and OS versions added in the future as additional testing >>> and bug fixes allow. More broadly while there is no timeline commitment >>> from Firefox or Safari both browsers are known to be actively implementing >>> WebGPU and are anticipated to ship once their implementations are >>> sufficiently conformant. >>> >>> Sample links >>> https://github.com/austinEng/webgpu-samples >>> >>> Estimated milestones >>> Shipped on desktop 113 >>> OriginTrial desktop last 114 >>> OriginTrial desktop first 94 >>> Shipping on Android 121 >>> DevTrial on Android 111 >>> >>> Anticipated spec changes Discussion on the core WebGPU and WGSL >>> specification has been minimal since the API was shipped on desktop, with >>> most ongoing discussion centered around additional features that can be >>> layered onto the API. While we are still open to minor spec bug fixes at >>> this point the overwhelming majority of the spec should see no behavioral >>> changes. >>> >>> Link to entry on the Chrome Platform Status >>> https://chromestatus.com/feature/5119617865613312 >>> >>> Links to previous Intent discussions Intent to prototype: >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/dxqWTSvyhDg/m/1UDaFD17AQAJ >>> -- >>> 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/CAEGwwi0ReGtfej_JbQPVHEbutrB%3DpDsEOdg9kfHTHYpyojkA-A%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEGwwi0ReGtfej_JbQPVHEbutrB%3DpDsEOdg9kfHTHYpyojkA-A%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%2Bw_GhVyOHxxj0y6%3DcLKCpGA5djpiowWQyBE12mNsXpWnHw%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_GhVyOHxxj0y6%3DcLKCpGA5djpiowWQyBE12mNsXpWnHw%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/25bb3d84-fc08-4526-b686-ee9b2e9e8b77%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/25bb3d84-fc08-4526-b686-ee9b2e9e8b77%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEGwwi3e%3D%3DgerCPhJ5tspNh5nv93trpj3PNSeB7V528h0utTkw%40mail.gmail.com.
