W3C home > Mailing lists > Public > www-style@w3.org > December 2010

Re: [css3-transitions] Interpolating 'other' value types

From: Chris Marrin <cmarrin@apple.com>
Date: Wed, 01 Dec 2010 11:43:38 -0800
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-id: <E4E7C3C5-0AC2-4C7B-B96B-36A65C6953C4@apple.com>
To: Simon Fraser <smfr@me.com>

On Nov 30, 2010, at 3:25 PM, Simon Fraser wrote:

> On Nov 30, 2010, at 2:49 PM, Tab Atkins Jr. wrote:
>> Right now, the Transitions spec still says that only certain types of
>> values can be transitioned.  Other types of values are ignored (merely
>> kept in the transition-property list to maintain relative list
>> positions).
>> I thought we'd agreed to let any property without specified transition
>> rules transition, with the rule that it's equal to the start value at
>> t=0 and the end value at t>0 (or the opposite, whatever)?  Part of the
>> reason we introduced the step timing-function was specifically to help
>> control this case, if I recall correctly.
>> I assume this is just a temporary omission, and the necessary edits
>> will be made in time?
> David Baron suggested that transition-delay should apply to all properties.
> I said that I supported that in principle, but was worried about implementation
> performance implications, given that the default for transition-property is "all".

Maybe we've discussed this in the misty past, but why is the default 'all'? Wouldn't 'none' avoid expensive (in terms of processing) mistakes?

Received on Wednesday, 1 December 2010 19:44:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:41 UTC