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

Re: [css3-2d-transforms] 2D Transforms feedback

From: Dean Jackson <dino@apple.com>
Date: Sat, 31 Oct 2009 11:13:41 +1100
Cc: "www-style@w3.org" <www-style@w3.org>
Message-Id: <F7C5E1D9-D1D9-478C-92D0-33CE0ED21F62@apple.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Hi Sylvain,

Answering parts of your feedback here.

On 01/10/2009, at 6:43 AM, Sylvain Galineau wrote:

> 3. What are common use-cases for the Point interface and Window  
> object extensions defined in section 7 ? Is this the way one would  
> converts mouse event coordinates into a transformed node's  
> coordinate space for instance ?

Correct. As Řyvind notes elsewhere, these methods are a little weird.  
They probably should be in CSSOM View.

> 4. Also regarding section 7, interested in answers to  Řyvind  
> Stenhaug's earlier question here: http://lists.w3.org/Archives/Public/www-style/2009Sep/0120.html

I'll answer that one directly, but the summary would be that yes, we  
know they are deprecated. But there hasn't been any proposal for a  
replacement - the CSS OM specification seems stalled. Do you have any  
suggestions?

> 5. Valid input ranges for transform functions should be specified  
> e.g. can scale parameters be negative ?

Good point. Negative values should be allowed for scale.

> Safari 4 seems to ignore the sign if the input is negative.

This sounds like a bug. I know it works in some cases though, since  
I've used it in public examples.

Dean

>
> [1] http://www.w3.org/TR/css3-2d-transforms/
> [2] http://www.w3.org/TR/css3-2d-transforms/#dom-interfaces
>
>
>
Received on Saturday, 31 October 2009 00:14:16 GMT

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