> It is useful, but I don't think it's worth the trouble and I
> personally don't use it. IE's DOM is one example of what makes custom
> attributes troublesome - you never know which issues you will run into
> due to every custom attribute ending up as a property of an element.
> What if attribute name (which becomes a property name) is a reserved
> word (according to ECMAScript/JScript)? What if it corresponds to some
> IE's proprietary element property? Which of them takes precedence and
> which issues it might cause? etc.
>

I completle confused at finally - where to store elements metadata?
What is the best way?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to 
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to