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

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

From: Kang-Hao (Kenny) Lu <kennyluck@w3.org>
Date: Tue, 29 Mar 2011 08:53:27 +0900
Message-ID: <4D911F77.6060106@w3.org>
To: WWW Style <www-style@w3.org>
(11/03/29 7:43), Dean Jackson wrote:
> [snip]
> I understand this, but the problem is that transforms don't really
> work this way. As an author, you need to decide the order of transform
> functions. If the specification decided one way, then there would be a
> bunch of people who wanted it another way.
> It might be possible to add three new properties that are applied
> before the regular transform property. 'transform-scale' '-rotate'
> '-translate'. This would probably address your need in the simplest
> manner, and would be easy to implement. We'd define the order.

I think this is what David tried to propose in the earlier response not
Aaron's idea 1), although I have two comments.

1) I think these '-scale' and so on should happen after 'transform' as I
think it is more intuitive that way, Any reason why these should happen
before 'transform' ?

2) The fact that these "longhand" work differently from other
"longhand"s would probably confuse some people.

In light of this, what about a new property called "also-transform",
which cascades separately and happens after "transform"? This idea can
be extended to "also-background" and is sort of a solution to ISSUE-177,
but as this looks ugly, I wouldn't say I really like this solution.

I think this might be a use case that the CSS Mixin module (if we create
it) might want to address. A less uglier might look like "+transfrom:

Received on Monday, 28 March 2011 23:51:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:44 UTC