W3C home > Mailing lists > Public > public-fx@w3.org > April to June 2014

Re: [css-transforms] translation values without units

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 23 May 2014 14:26:29 -0700
Message-ID: <CAAWBYDD3VfCvDfe0TEUJEd7e+JXZzhRDGTyEgdc9Hodz0pCLUQ@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: FX <public-fx@w3.org>, "www-style@w3.org" <www-style@w3.org>
On Fri, May 23, 2014 at 2:05 PM, Dirk Schulze <dschulze@adobe.com> wrote:
>> Assuming that <translation-value> can always be converted into a
>> <length>
> WebKit allows unit less length values for translation values. Means:
> translate(20, 20);
> translateX(20);
> translateY(20);
> are accepted by the CSS parser even if the parser is not in SVG attribute mode. The spec reflects that with <translation-value>.
> This is not the case for Firefox, Blink (not even for -webkit-transform) or IE. We probably should change the spec and replace <translation-value> with <length>. Opinions?

Oh, is that what <translation-value> is supposed to be - just a
"<length> | <number>"?  That doesn't appear to be defined anywhere in
the draft right now.

Received on Friday, 23 May 2014 21:27:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:49 UTC