#1063: WebGPU Compatibility Mode
Discussions
Log in to see TAG-private discussions.
Discussed
Mar 1, 2025 (See Github)
punted
Discussed
Apr 1, 2025 (See Github)
Matthew: It was a Google Doc, now it's a proper explainer … looks like Martin is satisfied with this … Lola, do you think what Martin says? Lola: Defer to Martin, he has reviewed it and has the technical knowledge … I think it's a positive thing Matthew: We haven't given them actual feedback until now Lola: Problem 4 is what we should discuss with them … should encourage them to do the S&P questionnaire again Matthew: Was confused about the name, polarity of naming seems wrong to me … may have to read it again Lola: Its possible that the proposal increases fingerprinting surface Hadley: Agree with Lola, close with "generally happy", note that S&P responses are for earlier work … we think it would be helpful for it to update it for compatibility mode … but not block it … would mark it as resolution: satisfied … who is going to write the closing comment? Matthew: Will try to draft closing comment, but I'm away next week Hadley: Will place a comment in the issue. Matthew: Fairly simply comment, we shouldn't keep them waiting Xiaocheng: Are they aware that this is an early review? Hadley: We should point that out
OpenedMar 4, 2025
Hola, TAG!
I'm requesting a TAG review of WebGPU Compatibility Mode.
WebGPU Compatibility Mode is an opt-in, lightly restricted subset of WebGPU capable of running older graphics APIs such as OpenGL and Direct3D11. The goal is to expand the reach of WebGPU applications to older devices that do not have the modern, explicit graphics APIs that core WebGPU requires. This requires Compatibility Mode to prohibit the use of some WebGPU features that the older APIs do not support.
Further details: