On Mon, Jan 8, 2024 at 11:01 AM Yoav Weiss <[email protected]> wrote:
> > > On Fri, Jan 5, 2024, 14:19 Corentin Wallez <[email protected]> wrote: > >> Contact [email protected] >> >> ExplainerNone >> >> Specification >> https://gpuweb.github.io/gpuweb/#dom-gpustoragetextureaccess-read-write >> > > Is there a way for developers to feature detect support for this extra > value? > > Yes. All they have to do is check wgslLanguageFeatures <https://gpuweb.github.io/gpuweb/#gpuwgsllanguagefeatures> as below. if (navigator.gpu.wgslLanguageFeatures.has("readonly_and_readwrite_storage_textures")) { // Read-only and read-write storage textures are supported! } >> Summary >> >> Functionality added to the WebGPU/WGSL spec after its first shipment in a >> browser. Adds support for (read-only and) read-write storage textures which >> allow more general access to texture memory for GPU computation and can >> unlock more advanced graphical algorithms. This feature has been request by >> developers very often. >> >> >> Blink componentBlink>WebGPU >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebGPU> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> Read-write storage textures have not yet been implemented in any browser, >> but have been approved by the GPU for the Web Community Group, with >> representatives from Chrome, Firefox, and Safari. >> >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/948) >> >> *WebKit*: Positive ( >> https://github.com/WebKit/standards-positions/issues/294#issuecomment-1877411933) >> Note that this is a blanket approval from Safari for additions to the v1 >> WebGPU/WGSL spec. >> >> *Web developers*: Strongly positive One of the most requested additional >> features for WebGPU. >> >> *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 at the moment, WebGPU currently does not ship on Android WebView. >> >> >> 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, 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. Note that tests are still being written, but the feature will >> not be launched until it is fully tested. >> >> >> Flag name on chrome://flagsNone >> >> Finch feature nameNone >> >> Non-finch justificationNone >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/dawn/issues/detail?id=1972 >> >> Availability expectationFeature is available only in Chromium browsers >> for the near future, on the order of months. Other browsers intend to ship >> WebGPU support, but don't have specified timelines. >> >> Non-OSS dependencies >> >> Does the feature depend on any code or APIs outside the Chromium open >> source repository and its open-source dependencies to function? >> No >> >> 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/6469283075063808 >> >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGdfWNOqjLmKdMXiOK3xxDQ3j5Tm%3DdCo5i2jOGC4ULyY4fQ24w%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGdfWNOqjLmKdMXiOK3xxDQ3j5Tm%3DdCo5i2jOGC4ULyY4fQ24w%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/CAOmohSJq8O0%2BvYgQ6VCyJhEK7iRpBnG%2B4h2Npf4QJ5bLnzHAzA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSJq8O0%2BvYgQ6VCyJhEK7iRpBnG%2B4h2Npf4QJ5bLnzHAzA%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/CAPpwU5KG8Aedr6XMLE1BHND2%2B9MRjq1AXcnxkri5b9fEDYGiNw%40mail.gmail.com.
