Re: [css3-2d-transforms] Implementation report from Aryeh Gregor on 2012-02-08 (www-style@w3.org from February 2012)

From: Aryeh Gregor <ayg@aryeh.name>
Date: Wed, 8 Feb 2012 11:44:01 -0500
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: www-style@w3.org
Message-ID: <CAKA+Ax=+r1dKdkHCwrzO7xV+pdRzEo5Su9W5tsHy4PEEh_=2+Q@mail.gmail.com>

On Wed, Feb 8, 2012 at 11:03 AM, Simon Sapin <simon.sapin@kozea.fr> wrote:
> I only had two minor issues that were already reported here:
>
> 1. e and f in matrix(a,b,c,d,e,f) really are lengths, not unit-less numbers

They are logically lengths, but nobody allows that except Gecko.  By
the same logic, entries 4, 8, and 12 in matrix3d() have units of
1/length, which CSS doesn't support.  In practice, they're unitless
numbers that are interpreted as pixels.

> 2. The syntax for transform-origin should probably be unified with
> background-position.

This conflicts with 3D transform-origin:
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=15432>

Received on Wednesday, 8 February 2012 20:51:14 UTC