You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You currently need to specify the custom property type as a string, e.g. syntax: "<length> | auto", but now that <syntax> exists, it would be nice to just do syntax: <length> | auto.
We'd still allow string-wrapped types for legacy reasons, making the grammar syntax: <syntax> | <string>.
Note that <syntax> is wrapped in type() in some other cases:
In attr(), the <syntax> part must always be wrapped in type().
In @function, the <syntax> part may appear unwrapped when it's a single <syntax-component>, otherwise it must be wrapped in type().
However, I think such a wrapper would be redundant for the syntax descriptor (e.g. syntax: type(<length> | auto);), so I suggest that we just stick to the bare/unwrapped <syntax>.
The text was updated successfully, but these errors were encountered:
You currently need to specify the custom property type as a string, e.g.
syntax: "<length> | auto"
, but now that <syntax> exists, it would be nice to just dosyntax: <length> | auto
.We'd still allow string-wrapped types for legacy reasons, making the grammar
syntax: <syntax> | <string>
.Note that
<syntax>
is wrapped intype()
in some other cases:<syntax>
part must always be wrapped intype()
.<syntax>
part may appear unwrapped when it's a single <syntax-component>, otherwise it must be wrapped intype()
.However, I think such a wrapper would be redundant for the
syntax
descriptor (e.g.syntax: type(<length> | auto);
), so I suggest that we just stick to the bare/unwrapped<syntax>
.The text was updated successfully, but these errors were encountered: