Changes between Version 3 and Version 4 of SVG properties

Timestamp:

Mar 7, 2019, 1:41:20 PM (6 years ago)

Author:

Said Abou-Hallawa

Comment:

--

SVG properties

@@ -10 +10 @@
 2. It is a reflection of a DOM attribute. This means, setAttribute() should, affect the SVG property once it is called. Also getAttribute() should reflect the latest changed value of the SVG property. Let's call updating the SVG property from the attribute 'synchronize'. And let's call updating the attribute from the SVG property 'commit'
 3. Most of the properties are animated properties. The animated property has two members baseVal() and the animal(). Each of them are from the same SVG property type.  animal() differs from baseVal() only when animating. Otherwise they have to be the same value.
-4, The animal() of the animated property is read only property.
+4. The animal() of the animated property is read only; no changes from the DOM is allowed.
 5. The SVG property can be attached to an SVGElement or it can be detached.
+
+What things to consider for storing, modifying and animating the SVG property?
+
+1. It has to be RefCounted because the DOM object will encapsulate the same SVG property and this DOM object can outlive the owner element.
+2. Some properties are SVG lists of SVG types, e.g. SVGNumberList and SVGPointList. In addition of having the SVGNumberList itself Refcounted, all the items themselves have to be RefCounted also. The items can outlive the owner list itself.
+3.