Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For dynamically created elements I have noticed element.setAttribute(onClick,myFunction) doesn’t works properly in IE, whereas element.onclick=myFunction works in all browsers. Are there any functional differences also apart from this browser difference?
In theory, setAttribute takes a string and assigns it to an attribute, this then gets mapped to any associated DOM properties. In IE 7 and lower (and in IE 8 in IE 7 compatibility mode and in Quirks mode), it assigns a value directly to a DOM property of the same name (rendering it case sensitive and useless when the property expects something other than a string value).
The onfoo series of DOM properties take a function.
It is generally preferred to use attachEventListener and friends instead, and to use an abstraction layer (such as provided by YUI, jQuery, etc) to assign the values. This is generally easier. Such libraries also tend to include features to work around memory leak related bugs.