This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Need to allow unitless 0 as an argument to rotation functions.
Maybe no need to change this if Values and Units changes to allow unitless 0 for angles, as just resolved.
> Maybe no need to change this if Values and Units changes to allow unitless 0 for angles, as just resolved. Unitless zero for angles is allowed by CSS2.2 and CSS Values and Units Module Level 3 https://www.w3.org/TR/CSS22/aural.html#angles > Like for <length>, the unit may be omitted, if the value is zero: '0deg' may be written as '0'. https://www.w3.org/TR/css-values-3/#angles > ... However, for zero angles the unit identifier is optional (i.e. can be syntactically represented as the number 0). ... Also spec has it's own <angle> definition (influenced by SVG) and it's confusing. https://www.w3.org/TR/css-transforms-1/#svg-angle > An angle can be a <number> without an unit identifier. In this case the number gets interpreted as a value in degrees. I think, the last one should be a separate issue.
My bad, the <angle> definition in the spec is about values in `transform` atrribute on SVG elements. So it doesn't affect <angle> definition for CSS. Also I found that the spec says (https://www.w3.org/TR/css-transforms-1/#transform-functions): > ... Wherever <angle> is used in this specification, a <number> that is equal to zero is also allowed, which is treated the same as an angle of zero degrees. That's equivalent to CSS2.2 and Values and Units Module. Looks like issue is resolved.
CSS WG resolved that unitless 0 was OK everywhere.