- From: Chris Marrin <cmarrin@apple.com>
- Date: Wed, 27 Oct 2010 16:03:47 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: Sylvain Galineau <sylvaing@microsoft.com>, www-style list <www-style@w3.org>
On Oct 27, 2010, at 2:01 PM, "L. David Baron" <dbaron@dbaron.org> wrote: > On Wednesday 2010-10-27 20:33 +0000, Sylvain Galineau wrote: >>> From: Chris Marrin [mailto:cmarrin@apple.com] >>> On Oct 27, 2010, at 1:21 PM, L. David Baron wrote: >>>> On Wednesday 2010-10-27 13:17 -0700, Chris Marrin wrote: >>>>> If so, then the rule would be that a 'none' in the list would turn >>>>> off transitions on all properties. The corresponding duration >>>>> would be ignored. An 'all' would turn transitions on for all >>>>> properties and would set their duration to the corresponding one. >>>>> Specific property names later in the list would override these. >>>>> That seems like the most logical rule to me. >>>> >>>> Are you're saying you'd want an occurrence of 'none' to override >>>> values earlier/later in the list, or just that 'none' would trigger >>>> transitions on no properties (and thus cause an item in the >>>> duration/timing-function/delay lists to be skipped)? >>> >>> I mean that if you were to say: >>> >>> transition-property: width, none, height; >>> transition-duration: 1s, 1000000s, 2s; >>> >>> you'd get a transition just on height and it would occur over 2s. >>> Similarly, if you say: >>> >>> transition-property: width, none, all, height; >>> transition-duration: 1s, 2s, 3s, 4s; >>> >>> you'd get a transition of 3s on all properties except height, which >>> would transition over 4s. >>> >> That is my expectation as well i.e. none/all override all the transitions >> that come before them in the property list. Subsequent properties can >> then declare expections to none/all. >> >> And if you have 'none,none' or 'all,all', normal dupe handling also >> happens so the last one wins. > > I'd have expected that overriding for 'all', since it "matches" all > properties, and the last one wins, but I wouldn't have expected that > overriding for 'none' since it matches no properties. > Hmm. I've always thought of 'none' as meaning "I don't want anything to animate". But I get your interpretation from a CSS matching standpoint. I guess it could go either way. But I do like the symmetry of my interpretation. With your interpretation 'none' would simply be a placeholder and would never affect the set of transitions. That could be useful. I would be fine with either interpretation. ~Chris chris@marrin.com
Received on Wednesday, 27 October 2010 23:04:27 UTC