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: Lea Verou <leaverou@gmail.com>
Date: Mon, 06 Feb 2012 01:29:04 +0200
Message-ID: <4F2F10C0.5090609@gmail.com>
To: robert@ocallahan.org
CC: Dean Jackson <dino@apple.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
On 5/2/12 23:56, Robert O'Callahan wrote:
> There is a ton of usage of the unprefixed version already, and I bet
> much of it doesn't use commas since it's just copied and pasted from
> whatever worked in Webkit.
>
> We don't have the freedom to change the unprefixed syntax in
> incompatible ways.

Then why did we change the gradient syntax in incompatible ways? How is 
that different?

And what's the point of WD and prefixes if backwards compatibility is 
that big an issue even in that case? If nothing can change in transforms 
any more, why doesn't it move to CR?

There is a recent thread on this list by Tab & fantasai about review of 
functional notation in CSS, pretty much everything suggested there would 
also break backwards compatiblity in incompatible ways just as much.

-- 
Lea Verou (http://lea.verou.me | @LeaVerou)
Received on Monday, 6 February 2012 04:59:13 GMT

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