Skip to content

Conversation

@ChrisC
Copy link
Contributor

@ChrisC ChrisC commented Dec 15, 2025

I opted to batch classifications for "is" and "where" web features in one PR, since they are so closely related.

To maintain a singular focus of tests per classified feature, I opted to exclude the following:
css/selectors/ (root):

  • is-where-basic.html
  • is-where-error-recovery.html
  • is-where-not.html
  • is-where-pseudo-classes.html
  • is-where-pseudo-elements.html
  • is-where-shadow.html
  • is-where-visited.html
  • is-where-error-crash.html

css/selectors/parsing/:

  • parse-is-where.html

css/selectors/invalidation/:

  • is-where-pseudo-containing-hard-pseudo.html
  • is-where-pseudo-containing-hard-pseudo-and-never-matching.html

If there are suggestions for how to handle these cross-cutting tests, I'm open to suggestions!


As of 2025-12-05, the wpt-pr-bot is requesting reviews from code owners for changes to WEB_FEATURES.yml files. To learn more about the purpose of these files, check out this presentation from TPAC 2025, Annotating WPT to Surface the Status of the Platform

@ChrisC
Copy link
Contributor Author

ChrisC commented Dec 15, 2025

cc @foolip @jcscottiii

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants