maps "is" and "where" web features #56766
Open
+29
−0
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.
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.htmlis-where-error-recovery.htmlis-where-not.htmlis-where-pseudo-classes.htmlis-where-pseudo-elements.htmlis-where-shadow.htmlis-where-visited.htmlis-where-error-crash.htmlcss/selectors/parsing/:parse-is-where.htmlcss/selectors/invalidation/:is-where-pseudo-containing-hard-pseudo.htmlis-where-pseudo-containing-hard-pseudo-and-never-matching.htmlIf 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