Skip to content

Commit d3c7da4

Browse files
committed
[css-properties-values-api] Rewrite conditional rules segment to be entirely a note, explaining the relevant behavior by pointing to the specs that define it.
1 parent d1335e2 commit d3c7da4

File tree

1 file changed

+18
-6
lines changed

1 file changed

+18
-6
lines changed

css-properties-values-api/Overview.bs

+18-6
Original file line numberDiff line numberDiff line change
@@ -704,12 +704,24 @@ Otherwise, the interpolation falls back to the default 50% flip described in
704704
Conditional Rules {#conditional-rules}
705705
--------------------------------------
706706

707-
''@supports'' rules and the {{CSS/supports(conditionText)}} method behave as specified
708-
in [[!css-variables]].
709-
710-
Note: In other words, for the purpose of determining whether a value is
711-
supported by a given custom property, the type registered for the custom property is
712-
ignored and any value consisting of at least one token is considered valid.
707+
=======
708+
<div class=note>
709+
''@supports'' rules and the {{CSS/supports(conditionText)}} method
710+
behave as specified in [[!css-variables]],
711+
without distinguishing between registered and unregistered custom properties,
712+
and paying no attention to registered properties' syntaxes.
713+
714+
{{CSS/supports(property, value)}},
715+
as specified in [[css-conditional-3]],
716+
<em>does</em> pay attention to the syntax of registered custom properties.
717+
718+
The general principle in use
719+
is that anything which evaluates the validity of a CSS property value on its own
720+
will pay attention to the syntax of registered custom properties,
721+
but anything parsing any larger construct
722+
(such as declarations, or entire stylesheets)
723+
will ignore the syntax.
724+
</div>
713725

714726
Relative URLs {#relative-urls}
715727
------------------------------

0 commit comments

Comments
 (0)