W3C home > Mailing lists > Public > www-style@w3.org > March 2011

Re: [css3-2d-transforms] "longhand" for the transform stack

From: fantasai <fantasai.lists@inkedblade.net>
Date: Thu, 24 Mar 2011 15:38:13 -0700
Message-ID: <4D8BC7D5.8060701@inkedblade.net>
To: Aaron Gustafson <aaron@easy-designs.net>
CC: "L. David Baron" <dbaron@dbaron.org>, www-style@w3.org
On 03/24/2011 03:14 PM, Aaron Gustafson wrote:
>
> That certainly makes sense and is something I hadn't considered, but I do still think we should look for some balance. On one
> hand there's the incredible power inherent in specifically ordering your transformations and on the other hand there's a
> desire to easily (and with limited repetition) being able to successfully manage ever more complex stacks of transformations.

Going back to your original problem statement:

> The issue(s): Based on the current model, it is difficult for authors to
> manage compound transforms for transitions as well as in the context of
> the cascade. This issue is exacerbated when it comes to dynamic manipulation
> (via script) because most browsers supporting transforms currently only
> expose the current transform state as a matrix, which is not human-readable.

I don't have any solutions for managing the cascade,
but for dynamic manipulation, it would probably make
the most sense to introduce better APIs for manipulating
the value of the 'transform' property.

As for the cascade, we have similar problems with multiple
shadows and backgrounds. Probably they should all be solved
in the same way.

~fantasai
Received on Thursday, 24 March 2011 22:38:52 GMT

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