You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: