W3C home > Mailing lists > Public > www-style@w3.org > August 2014

Re: [css-transforms] Adding specialized properties for simple transforms

From: Rik Cabanier <cabanier@gmail.com>
Date: Thu, 7 Aug 2014 09:54:06 -0700
Message-ID: <CAGN7qDCKk=vmwUv3LdVgZ3z1YBELZgeR3_vHanXctUMX1cqyaQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Dirk Schulze <dschulze@adobe.com>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
On Thu, Aug 7, 2014 at 12:12 AM, Tab Atkins Jr. <jackalmage@gmail.com>
wrote:

> On Thu, Aug 7, 2014 at 12:53 AM, Dirk Schulze <dschulze@adobe.com> wrote:
> > I think the origin bits are the interesting part for rotate and scale.
> As I understand Shane, he wants everything to be expressed in the
> untransformed coordinate space. So would be the expression of the origin.
> That means that we have to multiply the origin of scale (and for rotate as
> well) with the inverse of all previous transformations for the current
> element. Is it that what you mean Rik?
>
> Your transform list confused me, but I'll just say that what Shane
> wants is for the origins to work "independently", so that you don't
> have to think about the fact that t/s/r all exist and might apply when
> you're just trying to write one of them.  Whatever that implies for
> ordering of the translates used for origin hacks, that's what we want.


I agree.
If we keep the origin-per-transform, the spec will need to say that the
origins of scale and rotate need to be updated with the translatation.
Received on Thursday, 7 August 2014 16:54:34 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 7 August 2014 16:54:34 UTC