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
clip is defined in Masking 1 with rect() | auto. rect() is anchored to its definition below the clip property definition table: rect() = rect( <top>, <right>, <bottom>, <left> ). Lastly, clip is deprecated, it is the only property that uses <rect()> with this definition, and there is a new definition of <rect()> in Shapes 1:
Note: This syntax is similar, but not quite identical, to the legacy rect() function used solely by the clip property.
I believe that rect() in the clip property is ambiguous because it can be interpreted as a function component value named rect with no argument. A terminal or non-terminal must be defined between angled brackets, per the CSS value definition syntax.
To avoid declaring different value definitions for the same type, clip could be defined as rect( <top>, <right>, <bottom>, <left> ) | auto and the definition of <rect()> below the clip definition table could be removed or rewrited in a way that prevent @webref/css to extract it.
The text was updated successfully, but these errors were encountered:
clip
is defined in Masking 1 withrect() | auto
.rect()
is anchored to its definition below theclip
property definition table:rect() = rect( <top>, <right>, <bottom>, <left> )
. Lastly,clip
is deprecated, it is the only property that uses<rect()>
with this definition, and there is a new definition of<rect()>
in Shapes 1:I believe that
rect()
in theclip
property is ambiguous because it can be interpreted as a function component value namedrect
with no argument. A terminal or non-terminal must be defined between angled brackets, per the CSS value definition syntax.To avoid declaring different value definitions for the same type,
clip
could be defined asrect( <top>, <right>, <bottom>, <left> ) | auto
and the definition of<rect()>
below theclip
definition table could be removed or rewrited in a way that prevent@webref/css
to extract it.The text was updated successfully, but these errors were encountered: