W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: [css3-transforms] Making transform-origin a list, converting transform to comma separated

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 4 Feb 2012 02:19:42 -0800
Message-ID: <CAAWBYDAqHMzb4xdAhjTQPvkBw1Ku0zmzmyXB-J8LGZQMsrsVUw@mail.gmail.com>
To: Lea Verou <leaverou@gmail.com>
Cc: www-style list <www-style@w3.org>
On Fri, Feb 3, 2012 at 4:09 PM, Lea Verou <leaverou@gmail.com> wrote:
> We were discussing today with shepazu that there doesn't seem to be any
> reason for transform to be whitespace separated over comma separated, like
> other list-accepting properties (background, box-shadow, text-shadow,
> transition etc). It probably comes from SVG transforms, which are also
> whitespace separated, but it's inconsistent with the rest of CSS.

While comma separation would probably be appropriate, it's not
necessary for disambiguation here (unlike all the other examples
you've provided).


> While I'm at it, it would be great if transform-origin was also a comma
> separated list, being potentially able to accept different origins for every
> transform. As it currently stands, the only way to do that is wrapper
> elements. It's very useful, for example to make an element move in a
> circular path while not being rotated itself (two rotate transforms with
> different origins and opposite angles).

We should probably have an origin() transform or something that
affects all following transforms up to the next origin().

~TJ
Received on Saturday, 4 February 2012 10:20:37 GMT

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