Contact emails jiawei.s...@intel.com<mailto:jiawei.s...@intel.com>
Explainer The "clip-distances" GPU feature adds the WGSL built-in variable @builtin(clip_distances) to allow a vertex shader to output user-defined clip distances. https://github.com/gpuweb/gpuweb/pull/4588 Specification https://gpuweb.github.io/gpuweb/#dom-gpufeaturename-clip-distances Summary Adds the optional GPU feature "clip-distances" that allows setting user-defined clip distances in vertex shader outputs. This technique is particularly useful for the applications that need to clip all vertices in a scene that are beyond a user-defined plane, such as many CAD applications. Blink component Blink>WebGPU<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebGPU> TAG review None TAG review status Pending Risks Interoperability and Compatibility This feature has been approved in W3C GPU for the Web WG meetings including participants from Safari and Firefox. Related meeting minutes: https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2024-05-29#add-optional-feature-clip-distances-if-there-are-new-questions-4588 Gecko: No signal (Mozilla members have approved https://github.com/gpuweb/gpuweb/pull/4588 and 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/390) 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 Goals for experimentation Ongoing technical constraints 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, where hardware support is available. 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/issues/3773 Flag name on chrome://flags None Finch feature name WebGPU.Enabled:UnsafeFeatures Requires code in //chrome? False Tracking bug https://issues.chromium.org/issues/358408571 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5141929256550400 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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DM4PR11MB623701939A127A3BA2309335ED682%40DM4PR11MB6237.namprd11.prod.outlook.com.
