fix: recognize at-rule() feature queries in use-baseline - #533
Draft
Pixel998 wants to merge 2 commits into
Draft
Conversation
DMartens
reviewed
Aug 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prerequisites checklist
AI acknowledgment
What did you do?
What did you expect to happen?
No lint error, because
@scopeis guarded by its matching feature query.What actually happened?
use-baselinereported:What is the purpose of this pull request?
This PR makes
use-baselinerecognize@supports at-rule()feature queries, so at-rules used as progressive enhancements are not incorrectly reported as baseline violations.What changes did you make? (Give an overview)
at-rule()handling for@supportsconditions inuse-baseline.@supports at-rule()pattern.Related Issues
Blocked on eslint/csstree#148
Is there anything you'd like reviewers to focus on?