This feature is not Baseline because it does not work in some of the most widely-used browsers.
Secure context: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.
Note: This feature is available in Web Workers.
The reason read-only property of the GPUPipelineError interface defines the reason the pipeline creation failed in a machine-readable way.
An enumerated value that can be one of:
"internal"Pipeline creation failed because of an internal error (see GPUInternalError for more information about these kinds of error.)
"validation"Pipeline creation failed because of a validation error (see GPUValidationError for more information about these kinds of error.)
See the main GPUPipelineError page for an example involving a GPUPipelineError object instance.
| Specification |
|---|
| WebGPU> # dom-gpupipelineerror-reason> |
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Opera | Safari | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | WebView Android | WebView on iOS | |
reason |
113Currently supported on ChromeOS, macOS, and Windows only. |
113Currently supported on ChromeOS, macOS, and Windows only. |
141Currently supported on Windows only, in all contexts except for service workers. |
99Currently supported on ChromeOS, macOS, and Windows only. |
26 | 121 | No | 81 | 26 | 25.0 | 121 | 26 |
© 2005–2025 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/GPUPipelineError/reason