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

Re: [css3-transitions] suppression of transition starting, inheritance

From: Giovanni Campagna <scampa.giovanni@gmail.com>
Date: Thu, 11 Jun 2009 17:53:30 +0200
Message-ID: <65307430906110853m5b951901t9b2626535f9b82ce@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: www-style@w3.org
2009/6/11 L. David Baron <dbaron@dbaron.org>:
> On Thursday 2009-06-11 17:41 +0200, Giovanni Campagna wrote:
>> 2009/6/11 L. David Baron <dbaron@dbaron.org>:
>> > On Thursday 2009-06-11 16:38 +0200, Giovanni Campagna wrote:
>> >> A shorter method to describe processing model 2 is "Transitions
>> >> affects the Used Values, not the Computed Values. This means that
>> >> values in the middle of a Transition are never inherited.". It would
>> >> not break scripts anyway, because those query the CSS2.0 Computed
>> >> Value (now Used Value)
>> >
>> > No, that's very different from processing model (2), and would break
>> > transitions on inherited properties like 'color'.
>>
>> Why is it different?
>> Step 3) in particular ensures that "inherit" on child elements has the
>> value before the state change, until the end of transaction. So
>> Transition does not affect the Computed Value, or actually it delays
>> the propagation of CV changes to children.
>
> No, since the child elements will still inherit all the values over
> the course of the transition, including the one from step (5).

That would mean that transition progress causes the process to be
reinstantiated, because it triggers a style change?

> -David
>
> --
> L. David Baron                                 http://dbaron.org/
> Mozilla Corporation                       http://www.mozilla.com/
>
Received on Thursday, 11 June 2009 15:54:07 GMT

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