Re: [css3-transitions] transitions and rendering objects vs. DOM nodes

On Sat, Jun 27, 2009 at 11:44 AM, L. David Baron <> wrote:

> I have another question about transitions that I think ought to be
> addressed in the spec ( ),
> though in this case I'm not exactly sure how it should be addressed
> in the spec.
> This is the question of whether transition should be associated with
> a change in style on a content node, or a change in style on a
> rendering object (a box).  Either solution poses a bunch of
> problems.
> If transitions are associated with the style on an element (DOM
> node), then we have problems in any case where a content node has
> more than one style.  The main case of this I can think of is
> pseudo-elements.  For example, I think it's hard to do something
> sensible with:
>  p { color: gray; }
>  p::first-line { color: black; }
>  p:hover { color: blue; }
>  p:hover::first-line { color: aqua; }
>  a { transition: 3s color; }
> then it's really not clear what the transition on the anchor should
> be when the p goes into the :hover state (either when the anchor is
> split between the first line and the second, or when the anchor is
> entirely in the first line).

How about: if an element has a first-line or first-letter rule setting a
property on it, then transitions on that property are disabled for the
element and all its descendants.

"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah

Received on Monday, 29 June 2009 04:13:08 UTC