Repository navigation
Re-scopes at-rule - #1231
Re-scopes at-rule#1231
Conversation
Co-authored-by: Kevin Babbitt <kbabbitt@microsoft.com>
Co-authored-by: Kevin Babbitt <kbabbitt@microsoft.com>
Co-authored-by: Kevin Babbitt <kbabbitt@microsoft.com>
Removed use cases from the explainer. Detect whether an at-rule, with optional prelude and/or block, is supported based on this resolution: w3c/csswg-drafts#6966 (comment) Detect whether a given declaration is supported within an at-rule block based on the proposed @supports-condition w3c/csswg-drafts#12622 (comment)
| Allow authors to feature-detect new enhancements to existing at-rules, such as: | ||
| - New media query features and other additions to at-rule preludes | ||
| - New descriptors that may be introduced to rules such as `@font-face` | ||
|
|
There was a problem hiding this comment.
Rather than deleting these, should we move them to Non-Goals, with a note that the CSSWG resolved to introduce @supports-condition to handle them? And perhaps a link to the spec: https://drafts.csswg.org/css-conditional-5/#supports-condition-rule
- Addresses TAG comments found [here](w3ctag/design-reviews#1176 (comment)) - moves previous capabilities to non-goals based on the new `@supports-condition` at-rule
|
Kevin Babbitt (@kbabbitt) I've move the previous capabilities of at-rule to non-goals and added an additional paragraph to address TAG's review. |
| /* ... */ | ||
| } | ||
| ``` | ||
| ### Context Aware feature detection |
There was a problem hiding this comment.
I think this section should go as a sub-header under "Non-goals" similar to the one being added for @charset. Putting it here makes it seem like it's part of what we're supporting. Moving it up under "Non-goals" also sets up another edit I just noticed we need (comment incoming)
There was a problem hiding this comment.
There's no longer a "second form" with the changes that have been made. I can see two things we could do with it:
- Remove it entirely
- Change "the second form" to
@supports-conditionand repurpose this section as an example of a potential false positive mentioned in the non-goals section
Removed 2 use cases for the at-rule function based on 2 CSSWG resolutions.
"Detect whether an at-rule, with optional prelude and/or block, is supported" based on : [css-conditional-5] Add ability to test for at-rule preludes w3c/csswg-drafts#6966 (comment)
"Detect whether a given declaration is supported within an at-rule block" based on the proposed @supports-condition [css-conditional]
@supports-condition, for larger feature queries and named reuse w3c/csswg-drafts#12622 (comment)