LGTM3 On Thursday, April 10, 2025 at 12:40:03 AM UTC+9 Daniel Bratell wrote:
> LGTM2 > > /Daniel > On 2025-04-02 18:08, Alex Russell wrote: > > LGTM1, but would be good to see the other review sections started. > > On Wednesday, April 2, 2025 at 1:15:47 AM UTC-7 fbea...@google.com wrote: > >> Contact emails >> >> fbeauf...@google.com >> >> Explainer >> >> To simplify the copy of entire buffers, a new overload has been added to >> the GPUCommandEncoder copyBufferToBuffer() method, allowing developers to >> omit offsets and size parameters. >> >> >> https://github.com/gpuweb/gpuweb/pull/5098 >> >> Specification >> >> https://gpuweb.github.io/gpuweb/#dom-gpucommandencoder-copybuffertobuffer >> >> Summary >> >> Functionality added to the WebGPU spec after its first shipment in a >> browser. >> >> The GPUCommandEncoder copyBufferToBuffer() method now includes a simpler >> way to copy entire buffers using a new overload with optional offsets and >> size parameters. >> >> 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-03-19#make-the-last-2-arguments-to-copybuffertobuffer-optional-4807 >> >> 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/4807) >> >> 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 link: >> >> https://github.com/gpuweb/cts/pull/4310 >> >> Flag name on chrome://flags >> >> Experimental Web Platform Features >> >> Finch feature name >> >> WebGPUCopyBufferToBufferOverload >> >> Requires code in //chrome? >> >> False >> >> Tracking bug >> >> https://issues.chromium.org/issues/405883444 >> >> Estimated milestones >> >> DevTrial on desktop >> >> 136 >> >> DevTrial on Android >> >> 136 >> >> 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/5172397000622080?gate=5107250466914304 >> >> 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+unsubscr...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/74f3242c-fcd6-4bb8-82aa-3ddac4aa3125n%40chromium.org > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/74f3242c-fcd6-4bb8-82aa-3ddac4aa3125n%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+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/83a9afb5-9b9a-4369-b4e0-c50012b8c66dn%40chromium.org.
