@@ -117,12 +117,13 @@ Extensions to the ''@supports'' rule</h2>
117117 <pre class="prod def" nohighlight>
118118 <dfn><supports-feature></dfn> = <<supports-selector-fn>>
119119 | <<supports-font-tech-fn>> | <<supports-font-format-fn>>
120- | <<supports-at-rule-fn>>
121- | <<supports-decl>>
120+ | <<supports-at-rule-fn>> | <<supports-named-feature-fn>>
121+ | <<supports-decl>>
122122 <dfn><supports-decl></dfn> = ( [ <<declaration>> | <<supports-condition-name>> ] )
123123 <dfn><supports-font-tech-fn></dfn> = font-tech( <<font-tech>> )
124124 <dfn><supports-font-format-fn></dfn> = font-format( <<font-format>> )
125125 <dfn><supports-at-rule-fn></dfn> = at-rule( <<at-keyword-token>> )
126+ <dfn><supports-named-feature-fn></dfn> = named-feature( <<ident>> )
126127 </pre>
127128
128129 : <<supports-condition-name>>
@@ -150,6 +151,12 @@ Extensions to the ''@supports'' rule</h2>
150151 <a href="#dfn-support-at-rule">supports the at-rule</a>
151152 provided as an argument to the function.
152153
154+ : <<supports-named-feature-fn>>
155+ ::
156+ The result is true if the UA
157+ <a href="#dfn-support-named-feature">supports the named feature</a>
158+ provided as an argument to the function.
159+
153160<h3 id="support-definition-ext">
154161Extensions to the definition of support</h3>
155162
@@ -186,6 +193,23 @@ At-rules</h4>
186193 Note: Because ''@charset'' is not a valid [=at-rule=] ,
187194 it is not considered to be supported under this definition.
188195
196+ <h4 id="support-definition-named-features">
197+ Named features</h4>
198+
199+ A CSS processor is considered to
200+ <dfn export for=CSS id="dfn-support-named-feature">support an named feature</dfn>
201+ if it supports the named feature based on the feature definition
202+ described in the following list:
203+
204+ [ No features are currently defined. ]
205+
206+ If the feature is not listed the processor does not support the named feature.
207+
208+ Note: The CSS Working Group intends to add features to this list rarely,
209+ when there is real demand for feature testing something specific
210+ and it would be unreasonable to add a more general feature testing mechanism
211+ that would cover the use case.
212+
189213<h4 id="support-definition-supports-condition-name">
190214Named conditions</h4>
191215
@@ -2058,6 +2082,10 @@ Changes since the <a href="https://www.w3.org/TR/2024/WD-css-conditional-5-20241
20582082 <li> Made <<container-query>> optional
20592083 (<a href="https://github.com/w3c/csswg-drafts/issues/9192#issuecomment-1789850349">#9192</a> )
20602084 </li>
2085+ <li> Extended [=supports queries=] to express named features
2086+ via ''named-feature()'' .
2087+ (<a href="https://github.com/w3c/csswg-drafts/issues/9875">#9875</a> )
2088+ </li>
20612089</ul>
20622090
20632091<h3 id="changes-20240723" class="no-num">
@@ -2097,6 +2125,8 @@ Additions since Level 4</h3>
20972125 via ''font-tech()'' and ''font-format()'' .
20982126 <li> Extended [=supports queries=] to express at-rule capabilities
20992127 via ''at-rule()'' .
2128+ <li> Extended [=supports queries=] to express named features
2129+ via ''named-feature()'' .
21002130 <li> Moved Container Queries from [[CSS-CONTAIN-3]] to this specification.
21012131 (See also the [[CSS-CONTAIN-3#changes]] for more information
21022132 on the evolution of this feature.)
0 commit comments