Re: [css3-transforms] Extending CSSOM interface

Hi Aryeh,

On Feb 16, 2012, at 10:20 AM, Aryeh Gregor wrote:

> On Thu, Feb 16, 2012 at 12:57 PM, Dirk Schulze <dschulze@adobe.com> wrote:
>> Hi www-style,
>> 
>> I would like to see some changes to the current interfaces of CSS Transforms. This is also described in the Wiki "Merged Transforms"[0]. Currently CSS Transforms specifies 'CSSMatrix' and 'CSSTransformValue'.
> 
> But it defines no way to obtain either type of object:
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15443
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16003
At least for WebKit and Mozilla there is a way to get them: getPropertyCSSValue(). It should be the biggest concern of CSSOM to address that! In the meantime we can specify the interfaces and make sure that they work when all browsers support either getPropertyCSSValue or another way to access it from CSSOM.

I believe that this is one of the biggest outstanding issues on CSSOM. But it shouldn't block us to specify the interfaces right now. This is really important, since authors don't want to parse strings on their own to script transforms and an interface like that also avoids parsing on the browser and makes performance better!

On SVG we have quite some experience with it, and I don't need to say that all browsers support it there :).

> 
> First the spec needs to say how to get these objects.  Then it makes
> sense to talk about changing their definitions.  Does any browser
> engine other than WebKit implement either of them?
Wouldn't it be the perfect excuse not to implement it at this point of time for you? ;) And yes, for instance gecko does give you access to CSSOM - the same way like WebKit. We should define the interfaces sooner than later (and than maybe to late). Like I said there is a lot of experience for SVG implementations with that.

Greetings,
Dirk

Received on Thursday, 16 February 2012 18:43:31 UTC