29413 2016-01-31 23:07:09 +0000 Allow unitless 0 as a valid rotation value 2017-01-13 17:39:24 +0000 1 1 1 Unclassified CSS Transforms unspecified PC All RESOLVED FIXED P2 normal --- 1 smfr smfr ayg cmarrin dino dschulze eoconnor rdvornov smfr public-css-bugzilla oldest_to_newest 124775 0 smfr 2016-01-31 23:07:09 +0000 Need to allow unitless 0 as an argument to rotation functions. 124777 1 smfr 2016-01-31 23:22:10 +0000 Maybe no need to change this if Values and Units changes to allow unitless 0 for angles, as just resolved. 128338 2 rdvornov 2016-12-21 10:52:27 +0000 > 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. 128339 3 rdvornov 2016-12-21 11:08:09 +0000 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. 128372 4 smfr 2017-01-13 17:39:24 +0000 CSS WG resolved that unitless 0 was OK everywhere.