LGTM3, contingent on an official standards position disposition from Mozilla (but not blocking on what it is).
On Monday, April 14, 2025 at 7:13:00 AM UTC-7 Corentin Wallez wrote: > We don't have minutes for these out-of-band meetings, but we want a stable > reference that we can point at as well. From talking with the Mozilla > engineers working on WebGPU, this would require our API owners to talk with > their standard folks to come to some agreement there (though I don't know > who that might be so I can't start an email thread). > On Saturday, April 12, 2025 at 1:45:52 AM UTC+2 Mike Taylor wrote: > >> Is there a place to find meeting minutes where Mozilla stated this? Agree >> with Domenic that it would be good to have a stable reference. >> On 4/11/25 10:16 AM, Yoav Weiss (@Shopify) wrote: >> > LGTM2 >> >> On Fri, Apr 11, 2025 at 7:09 AM Domenic Denicola <dom...@chromium.org> >> wrote: >> >> LGTM1. Although, it would be good to have a canonical place to link to >>> for that Mozilla meta-position, just like you are already doing for the >>> WebKit meta-position. >>> >>> On Thursday, April 10, 2025 at 1:25:24 AM UTC+9 fbea...@google.com >>> wrote: >>> >> On Wed, Apr 9, 2025 at 5:59 PM Daniel Bratell <brat...@gmail.com> wrote: >>>> >>>>> * Gecko: No signal (Mozilla members have requested during weekly >>>>> standardization meetings that we postpone filing standard positions until >>>>> we reach Candidate Recommendation (CR) status in Q4.) * >>>>> >>>>> Doesn't this part creates a bit of a chicken-egg problem? Or am I >>>>> misunderstanding the process. Does it just mean that Mozilla has >>>>> delegated >>>>> all this to their WebGPU spec representatives? >>>>> >>>> >>>> Sorry. it should have said: "Mozilla members have requested during >>>> weekly standardization meetings that we don't file standard positions >>>> anymore as we reached Candidate Recommendation (CR) status." >>>> >>> /Daniel >>>>> On 2025-04-02 12:18, 'François Beaufort' via blink-dev wrote: >>>>> >>>> Contact emails >>>>> >>>>> fbea...@google.com >>>>> >>>>> >>>>> Explainer >>>>> >>>>> Some developers using WebGPU for video effects pipelines have proposed >>>>> allowing a compatible GPUTextureView (2D, single subresource) to be used >>>>> in >>>>> place of a GPUExternalTexture binding. This would simplify their shader >>>>> logic, which currently needs to handle both GPUExternalTexture (for >>>>> source >>>>> video) and GPUTextureView (for intermediate processing) and reduce the >>>>> need >>>>> to dynamically compile shaders depending on where the texture comes from. >>>>> >>>>> https://github.com/gpuweb/gpuweb/pull/5079 >>>>> >>>>> Specification >>>>> >>>>> >>>>> https://gpuweb.github.io/gpuweb/#ref-for-dom-gpubindgrouplayoutentry-externaltexture%E2%91%A6 >>>>> >>>>> Summary >>>>> >>>>> Functionality added to the WebGPU spec after its first shipment in a >>>>> browser. >>>>> >>>>> A GPUTextureView is now allowed to be used for an externalTexture >>>>> binding when creating a GPUBindGroup. >>>>> >>>>> Blink component >>>>> >>>>> Blink>WebGPU >>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebGPU> >>>>> >>>>> TAG review >>>>> >>>>> None >>>>> >>>>> TAG review status >>>>> >>>>> Not applicable >>>>> >>>>> Risks >>>>> >>>>> Interoperability and Compatibility >>>>> >>>>> This feature has not yet been implemented in any browser. It has been >>>>> approved by the GPU for the Web Community Group, with representatives >>>>> from >>>>> Chrome, Firefox, and Safari. See minutes at >>>>> https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2025-02-19#add-gputextureview-support-to-importexternaltexture-5068 >>>>> >>>>> and >>>>> https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2025-03-19#allow-using-a-texture-view-for-an-externaltexture-binding-5079 >>>>> >>>>> Gecko: No signal (Mozilla members have requested during weekly >>>>> standardization meetings that we postpone filing standard positions until >>>>> we reach Candidate Recommendation (CR) status in Q4.) >>>>> >>>>> WebKit: Positive ( >>>>> https://github.com/WebKit/standards-positions/issues/294#issuecomment-1877411933 >>>>> ) >>>>> >>>>> Web developers: Positive (https://github.com/gpuweb/gpuweb/issues/4504 >>>>> ) >>>>> >>>>> Other signals: >>>>> >>>>> 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 >>>>> >>>>> None >>>>> >>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>> Mac, Linux, ChromeOS, Android, and Android WebView)? >>>>> >>>>> No >>>>> >>>>> All platforms will eventually have support. Will immediately be >>>>> available on Android, Android WebView, ChromeOS, Mac, and Windows, since >>>>> those platforms already support WebGPU. Linux is planned to have WebGPU >>>>> support in the future, so this feature will become available when WebGPU >>>>> does. >>>>> >>>>> Is this feature fully tested by web-platform-tests >>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>> ? >>>>> >>>>> Yes >>>>> >>>>> WebGPU/WGSL have a conformance test suite ( >>>>> https://github.com/gpuweb/cts) that is regularly pulled into Chromium >>>>> and part of the testing of Dawn/Tint in Chromium. While the CTS can be >>>>> embedded in WPT, the WebGPU team opted to keep it separate in Chromium >>>>> testing to use a customized harness for robustness and performance. All >>>>> the >>>>> tests about this feature in WebGPU CTS can be found through the below >>>>> links: https://github.com/gpuweb/cts/pull/4304 and >>>>> https://github.com/gpuweb/cts/pull/4306 >>>>> >>>>> Finch feature name >>>>> >>>>> WebGPU.Enabled:EnabledToggles >>>>> >>>>> Requires code in //chrome? >>>>> >>>>> False >>>>> >>>>> Tracking bug >>>>> >>>>> https://issues.chromium.org/issues/398752857 >>>>> >>>>> Estimated milestones >>>>> >>>>> No milestones specified >>>>> >>>>> 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/5106732252266496?gate=5112699639562240 >>>>> >>>>> This intent message was generated by Chrome Platform Status >>>>> <https://chromestatus.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+...@chromium.org. >>>>> >>>>> >>>>> To view this discussion visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPpwU5JF6TSbcO1KSF_i70Q5YTRoxc6D6h9hECw9RxD%3DV0erQg%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPpwU5JF6TSbcO1KSF_i70Q5YTRoxc6D6h9hECw9RxD%3DV0erQg%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+...@chromium.org. >> >> >>> To view this discussion visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/392b5522-b601-4a1d-9140-2d55ecdbef37n%40chromium.org >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/392b5522-b601-4a1d-9140-2d55ecdbef37n%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+...@chromium.org. >> >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSKgQD14rXTiE8qFC8jt3Mwm%3DtCmvY4TPS6ZJKp%2BZaUdNA%40mail.gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSKgQD14rXTiE8qFC8jt3Mwm%3DtCmvY4TPS6ZJKp%2BZaUdNA%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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b6f6a846-a128-45d7-b73f-dfa0c9e5d025n%40chromium.org.
