Make WebGPU shuddup about compilation errors

[greggman]

I noticed that both chrome and firefox (not sure what happened to Safari's WebGPU), emit compilation errors for WebGPU when calling createShaderModule.

Personally, I'd like to be able to turn those message off. If I'm doing something like glslsandbox then I'm submitting a shader to be compiled every few keypresses and I'll be reporting the errors to the user myself so I'd like to be able to turn off the clutter spewed out the JavaScript console so I can see my own errors instead of having to hunt through them inside the haystack of WGSL errors.

Has there been any thought to:

(a) being more like WebGL where were errors not not reported, you have to query them

(b) adding a option to not report them

I certainly agree most WebGPU devs will want to see error messages but.... adding the few lines to see the errors is only a tiny amount of work and .... personally I'd like to format the messages myself and having them get spit out twice (once by the browser, once by me) makes my custom messages harder to see.

[Kangz]

I think it may be because both browsers default to printing unhandled errors in the console. For now I think you could silence the errors with push/popErrorScope but I agree that shader module compilation errors seem kinda special and this is very related to #2119

[kainino0x]

Now that we've added compilationInfo I think the browsers could just stop including the error output in the validation errors. Then instead of a whole wall of text you'll just see "Compilation of this shader failed". OTOH it would be nice if it were still easy to see the errors in dev tools (like with an expandable console message).

In any case I think it's all browser specific but we could consider putting a note in the spec about where errors would ideally be surfaced. (It doesn't even say anything about uncaptured errors being shown in the console - Firefox used to not show them IIRC.)