#1176: Incubation: @supports at-rule

Visit on Github

Opened Dec 9, 2025

Explainer

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AtRuleFeatureDetection/explainer.md

The explainer

Where and by whom is the work is being done?

Feedback so far

You should also know that...

No response

<!-- Content below this is maintained by @w3c-tag-bot -->

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1176

Discussions

Log in to see TAG-private discussions.

Discussed Dec 15, 2025 (See Github)

Christian: Think this is about feature detecting at-rules themselves, kind of meta-feature detection.

Lola: I will have a look at this.

Christian: I will join.

Discussed Jan 5, 2026 (See Github)

CHristian: Had a first look. Seems fine, but want to do another pass. Terminology and other things. This lets you detect @-rule support in the browser. Elaborate.

Yves: Is it an @-rule extension?

Martin: It extends @supports, with a new syntax. My only concern is, it looks fiddly. Documentation is going to important.

Discussed Jan 12, 2026 (See Github)

Christian: No update.

Lola: No update.

Comment by @christianliebel Jan 19, 2026 (See Github)

@diekus @kbabbitt Thank you for your proposal and the great explanation of the problem space. We have a question: The proposal states that at-rule() returns true if the at-rule name is recognized in any context. As you describe, this introduces the risk of contextual false positives. Did you evaluate context-aware detection? If so, why did you prioritize global recognition over contextual validity?

Comment by @kbabbitt Jan 19, 2026 (See Github)

@christianliebel We did consider context-aware detection. When we discussed this problem space at a CSSWG face-to-face meeting last fall, the group resolved to introduce a new @supports-condition as a way of both defining and naming (for reuse) complex support queries such as those that need to account for context, and to keep at-rule() simple as an author convenience. Discussion in https://github.com/w3c/csswg-drafts/issues/12622 and https://github.com/w3c/csswg-drafts/issues/6966#issuecomment-3205037703.