- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 24 Mar 2011 13:22:37 -0700
- To: Aaron Gustafson <aaron@easy-designs.net>
- Cc: www-style@w3.org
On Wednesday 2011-03-23 17:44 -0400, Aaron Gustafson wrote:
> Possible solution: Transform longhand.
>
> What if we could do something like this instead:
>
> #demo {
> transform: scale(2);
> }
> #demo.state-1 {
> transform-rotate: 45deg;
> }
> #demo.state-2 {
> transform-rotate: 90deg;
> }
>
> This is a simple example, but this concept would solve so many problems when
> it comes to managing complex transform stacks and would be incredibly
> helpful for managing CSS-based transitions.
The issue here is that the values of 'transform' are an *ordered*
list of transformations. For example, the following two transforms
are different:
translateX(100px) rotate(45deg)
rotate(45deg) translateX(100px)
So if we wanted longhand transform properties, we'd need to give the
one true order for the operations, and say how those operations
interacted with the ones in the 'transform' list (which *can't* be
decomposed into subproperties since it's an ordered list, and
decomposing it would lose that order).
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
Received on Thursday, 24 March 2011 20:23:09 UTC