W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: CSS Transforms : computed value

From: L. David Baron <dbaron@dbaron.org>
Date: Tue, 13 Jan 2009 12:19:42 -0800
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Cc: "www-style@w3.org" <www-style@w3.org>, hyatt@apple.com, Dean Jackson <dino@apple.com>
Message-ID: <20090113201942.GA25297@pickering.dbaron.org>

On Tuesday 2009-01-13 17:53 +0100, Daniel Glazman wrote:
> I strongly recommend keeping the computed value of 'transform' more
> humanly readable, in the form of a series of individual transformations
> rather than a single matrix. I do understand that means the layout
> engine has to store more information than just a single transformation
> matrix. But if you want real-life wysiwyg editors to implement this -
> and it seems web designers want it too - then it's almost a necessary
> cost, at least from out POV.

I'm curious why it's important to do this for the *computed* value.

Would the need to do this for the computed value also be solved by
an API that gives you the winning CSS declaration block for a given
(element,property) pair?


L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
Received on Tuesday, 13 January 2009 20:20:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:23 UTC