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
{{ message }}
Repository navigation
[css-values] Ambiguities with 0 valid for all dimensions #1162
<single-animation> = <time> || <single-timing-function> || <time> || <single-animation-iteration-count> || ...
"Note that order is important within each animation definition: the first value in each <single-animation> that can be parsed as a <time> is assigned to the animation-duration, and the second value in each <single-animation> that can be parsed as a <time> is assigned to animation-delay."
offset example
With the recent decision that 0 is a valid value for all dimensions,
offset: ray(180deg) 0;
becomes ambiguous: 0 is a valid value for both offset-distance and offset-rotate.
We didn't decide 0 was valid for all dimensions (unless I'm remembering wrong) - just lengths and angles.
That said, the 'offset' problem is definitely still valid.
(I really, really hate that the group resolved this way. Much better to keep the unitless-0 limited to lengths, with the few angle exceptions explicitly called out as exceptions. Maybe we can get this reversed, with evidence that it's causing grammar problems.)
Activity
tabatkins commentedon Apr 3, 2017
We didn't decide 0 was valid for all dimensions (unless I'm remembering wrong) - just lengths and angles.
That said, the 'offset' problem is definitely still valid.
(I really, really hate that the group resolved this way. Much better to keep the unitless-0 limited to lengths, with the few angle exceptions explicitly called out as exceptions. Maybe we can get this reversed, with evidence that it's causing grammar problems.)
tabatkins commentedon Apr 3, 2017
Agenda+ to discuss the above - generic "angles can have unitless 0 too" resolution is causing grammar problems. Can we revisit the decision?
Stylo - support image-orientation property
Stylo - support image-orientation property
Bug 1341758 - make Servo's image-orientation parser to be agreed with…
Auto merge of #16334 - chenpighead:stylo-image-orientation-support, r…
Auto merge of #16334 - chenpighead:stylo-image-orientation-support, r…
Stylo - support image-orientation property
Auto merge of #16334 - chenpighead:stylo-image-orientation-support, r…
Auto merge of #16334 - chenpighead:stylo-image-orientation-support, r…
servo: Merge #16334 - Stylo - support image-orientation property (fro…
servo: Merge #16334 - Stylo - support image-orientation property (fro…
9 remaining items
ewilligers commentedon May 25, 2017
I have added use counters to Blink. We will know in three months how often unitless 0 is being used in gradients and filter and transform.
CSS: Use count unitless 0 supplied as <angle>
CSS Motion Path: Web Platform tests for longhand parsing
CSS Motion Path: Web Platform tests for longhand parsing
CSS Motion Path: Web Platform tests for longhand parsing
CSS Conic Gradients: do not support unitless 0 angles
CSS Custom Properties: Angles do not support unitless 0
CSS: Remove support for unitless 0 angles in offset-rotate
CSS: Remove support for unitless 0 angles in offset-rotate
CSS: Remove support for unitless 0 angles in offset-rotate
Add WG resolution about unitless 0 to Images 4 (related to #1162)
servo: Merge #16334 - Stylo - support image-orientation property (fro…
servo: Merge #16334 - Stylo - support image-orientation property (fro…
servo: Merge #16334 - Stylo - support image-orientation property (fro…
servo: Merge #16334 - Stylo - support image-orientation property (fro…