Re: Questions on SVG DOM Change Propogation

On Tue, 09 Feb 2010 19:22:08 +0100, Patrick Dengler <>  

> Hi folks,
> We are seeing some differing behaviors across implementations on DOM  
> Propagation.  We'd like to nail the appropriate behaviors.  (forgive the  
> length again)


It would be helpful if the examples were full svg documents, feel free to  
check them into the public cvs here:

That's where we put tests that are mostly for discussing a particular  

> Scenario 7: Setting the baseVal of a target's animation value.
>     function setTarget(evt) {
>         var root =;
>         var a = root.firstChild.nextSibling;
>         var aniStr =;
>         alert(aniStr.baseVal);
>         aniStr.baseVal = "_foo";
>         alert(;
>     }
> Safari: Updates the link target.
> Firefox: Updates the link target (and open the new target in a tab  
> instead of a window).
> Opera: Does not support links.

I see no reason why the above shouldn't work in Opera, links (including  
the 'target' attribute) are supported.

This gave the same results in all the browsers I tested just now (safari,  
opera, firefox):

   data:image/svg+xml,<svg xmlns=""><a  
target="foo"/><script>var a = document.getElementsByTagName("a")[0]; var  
target =; alert(target.baseVal + ": should say foo");  
target.baseVal = "_bar"; alert( + ": should say  

Again, it would be good with a full testcase to help the discussions.


Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog:

Received on Tuesday, 9 February 2010 20:52:30 UTC