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

Re: Behaviour of SVGTransformable and it's objects

From: Jonathan Watt <jwatt@jwatt.org>
Date: Fri, 10 Mar 2006 04:34:39 +0000
Message-ID: <441101DF.2030607@jwatt.org>
To: www-svg@w3.org

I guess the behavior that makes sense to me (at this point at least :) is to 
have the objects that exist for unset attributes maintained, but to have objects 
that only exist when an attribute has a (non null valid string) value replaced 
by new objects every time the attribute is set.

For example, the object implementing the SVGPathSegList accessible through 
SVGAnimatedPathData:pathSegList exists even if the 'path' element's 'd' 
attribute hasn't been set. Therefore this object would be maintained even if 'd' 
is set to a new value. However, pathSegList.getItem() to return any objects 
would require that the 'd' attribute be set to some valid path data. Therefore 
all of those objects would be dropped from the list if the attribute is set to a 
new value and new objects would be created as necessary.

Received on Friday, 10 March 2006 04:34:41 UTC

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