[svg-developers] Re: any disadvantage to setting properties on DOM nodes?

2011-03-23 Thread t...@ymail.com
--- In svg-developers@yahoogroups.com, Jacob Beard jbeard4@... wrote: Are there hidden complexities involved in using DOM nodes to store data that I should be aware of? As I learned it's not guaranteed an implementation will allow arbitrary data to be stored in DOM nodes:

[svg-developers] Re: any disadvantage to setting properties on DOM nodes?

2011-03-23 Thread Holger Jeromin
Jacob Beard schrieb am 22.03.2011 23:21: I seem to remember that in IE6 and 7, it was considered dangerous to set properties on DOM nodes, because this would potentially lead to memory leaks. In modern, SVG-enabled browsers, is this still the case, or is it considered safe to set arbitrary

Re: [svg-developers] Re: any disadvantage to setting properties on DOM nodes?

2011-03-23 Thread Jacob Beard
Thanks for that. It seems like setting expando properties on DOM nodes is not portable or safe. It's too bad, as it seems like this would be the easiest way to associate a DOM node with some arbitrary JavaScript data. This would be a really useful and appropriate technique when the data model

Re: [svg-developers] Re: any disadvantage to setting properties on DOM nodes?

2011-03-23 Thread Jacob Beard
Hm, I'm just reading a bit more deeply here. It seems that all browser implementations of SVG allow expando properties to be set on DOM nodes, and it's only Batik that doesn't work. However, Cameron suggests a path to add this functionality, and Thomas even points out that the Lobo browser already