-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create an RFC for what material is and is not allowed in WPT #30
Comments
Tangentially, we also discussed the possibility of "tentative" directories and correspondingly a guidance like e.g. "a directory for a new API with only an explainer without a draft spec should be marked as tentative". I'm not sure if we should have a different RFC for "tentative" directories though cc @jgraham . |
@boazsender can I assign this to you? I don't think @web-platform-tests/wpt-core-team feel we are on the hook to resolve issues in this repo, just PRs. |
Also in regards to the specifics of MojoJS: web-platform-tests/wpt#16455 (comment) |
@foolip: sure thing! |
@boazsender I'm going to go ahead and close this issue now, but if you do still want to send an RFC for it, certainly that would be welcome! |
We lack a clear policy of when to accept/reject material.
Some further action is needed after the discussion at TPAC regarding "tests that depend on test-only APIs implemented using Mojo for Chromium, e.g. WebXR, WebUSB".
It seems like there was latent consensus that tests which can only be run in one browser engine and will never be able to run in multiple engines, should not be included in WPT. There was even linting recently written to address a case of this: web-platform-tests/wpt#18509.
The text was updated successfully, but these errors were encountered: