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

Re: [css3-transitions] edits to transitions spec

From: fantasai <fantasai.lists@inkedblade.net>
Date: Thu, 03 Dec 2009 10:14:42 -0800
Message-ID: <4B180012.5000007@inkedblade.net>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Giovanni Campagna <scampa.giovanni@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, www-style@w3.org
Tab Atkins Jr. wrote:
> On Tue, Nov 24, 2009 at 7:57 AM, Giovanni Campagna
> <scampa.giovanni@gmail.com> wrote:
>> Section 3, it says: "Implementations must not start a transition when
>> the computed value of a property changes as a result of declarative
>> (as opposed to scripted) animation. "
>> I read this as "changing the :hover state of an element must not start
>> a transition", which is obviously against the purpose of declarative
>> transitions (as opposed to script-controlled animations)
> 
> Note the word "animation" at the end of that sentence.  Changing the
> :hover state is not a declarative animation, and so doesn't fall under
> the scope of that sentence.

Actually, I think Giovanni's got a really good point. The distinction
we want here is triggering on changes to specified values, not changes
that only affect the computed value. And we want this limitation to
apply to scripting as well: triggering a transition on <span> because
I changed <p>'s color doesn't make any more sense if I do it via JS
instead of 'transition'.

~fantasai
Received on Thursday, 3 December 2009 18:15:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:22 GMT