[process] New required functionality must be implementable on Compat #5518
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also clarify what "implementable" means.
Contributor
|
Previews, as seen when this build job started (7884ec3): |
Kangz
approved these changes
Jan 15, 2026
Contributor
|
LGTM. The main thing I'd like to see is that proposals include an analysis of the Compat APIs in their investigations. Not sure that's covered by any process, though. |
SenorBlanco
approved these changes
Jan 15, 2026
Contributor
Author
|
This document says what we require of proposals made to WebGPU, and implicitly in order to show that a proposal is implementable on Compat, it'll have to explain how. |
mwyrzykowski
approved these changes
Jan 18, 2026
Contributor
Author
|
@jimblandy PTAL |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Compatibility Mode means we now care about OpenGL/ES and D3D11 for any non-optional functionality (like immediates,
unrestricted_pointer_parameters, etc.). Update the process doc accordingly.Also clarify where we're talking about optional vs. required functionality, and expand on the meaning of "implementable".