- From: David Singer <singer@apple.com>
- Date: Fri, 06 May 2011 17:29:55 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: Dean Jackson <dino@apple.com>, Sylvain Galineau <sylvaing@microsoft.com>, Simon Fraser <smfr@me.com>, "Eric A. Meyer" <eric@meyerweb.com>, "www-style@w3.org" <www-style@w3.org>
On May 6, 2011, at 17:27 , L. David Baron wrote: > On Friday 2011-05-06 16:43 -0700, David Singer wrote: >> >> On May 6, 2011, at 16:08 , L. David Baron wrote: >> >>> On Friday 2011-05-06 10:26 -0700, David Singer wrote: >>>> Are we sure that there are no >>>> parsing-depends-on-units-implying-type places in CSS? >>> >>> In addition to the gradients issue already pointed out, there's also >>> the 'animation' shorthand property, where in addition to an ordering >>> rule for animation-duration vs. animation-duration, there needs to >>> be a way of determining whether a '0' is for one of those properties >>> or is for animation-iteration-count. >>> >>> (I'm also not saying that there aren't others.) >> >> Thanks. One is plenty; it destroys any confidence that the >> number of cases is and always will be zero. This makes general >> unitless zeroes dangerous and complicates parsing to no useful >> effect. > > That said, I don't know of any examples that are already in CR, and > I suspect that there aren't any (due to the low use of non-length > units in drafts that are already in CR). So these are things that > we can fix. True. The safest is probably not officially allowing (or deprecating) unitless zeros AND making sure it's harmless and unambiguous if they occur... David Singer Multimedia and Software Standards, Apple Inc.
Received on Saturday, 7 May 2011 00:30:23 UTC