W3C home > Mailing lists > Public > www-svg@w3.org > March 2006

Behaviour of SVGTransformable and it's objects

From: Jonathan Watt <jwatt@jwatt.org>
Date: Thu, 09 Mar 2006 20:43:38 +0000
Message-ID: <4410937A.6020000@jwatt.org>
To: www-svg@w3.org

Dear SVG WG,

While thinking through the refactoring of Mozilla's SVG implementation we were 
wondering what should happen to the DOM objects under SVGTransformable's 
'transform' attribute when the SVG element's XML 'transform' attribute is 
changed using setAttributeNS. Should the objects be replaced with new objects? 
Or should any of the objects be maintained and, if so, which?

I believe it makes most sense to maintain the SVGAnimatedTransformList and 
SVGTransformList objects, but to create new SVGTransform objects. I've written a 
test to see how current implementations behave, and those that implement 
SVGTransformable and that I have access to (Moz, Batik, Opera 9 build 8246) seem 
to agree. You can find the test at:


Perhaps you could add it to the SVG test suite and spec out this behavior if you 
agree with it?

Received on Thursday, 9 March 2006 20:50:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:07 UTC