- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 11 Jun 2009 11:59:22 -0400
- To: Giovanni Campagna <scampa.giovanni@gmail.com>
- Cc: www-style@w3.org
On Thursday 2009-06-11 17:53 +0200, Giovanni Campagna wrote: > 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? No, because of what I said in the second paragraph of the original message at http://lists.w3.org/Archives/Public/www-style/2009Jun/0121.html It's also clear in the spec that transitions do affect computed values: http://dev.w3.org/csswg/css3-transitions/#transitions- -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/
Received on Thursday, 11 June 2009 16:00:02 UTC