I have an application that uses a custom ajax library to inject xml generated
by a control using an httphandler. What I've run into is a problem with
javascript as an attribute value.

The following line of code used to work
e.setAttribute(attributes[i].nodeName, new Function(attributes[i].nodeValue));
where attributes[i].nodeName = "onclick" and attributes[i].nodeValue =
"jsfunction('value'); return false;"

ie8 in standards mode renders this as onclick="[object]" and this just
throws a javascript error when the user clicks on it
ie8 in compatibility mode renders this correctly as
onclick="jsfunction('value'); return false;" This works correctly for the
user.

Can anyone point me in the right direction in javascript to
1) identify ie8 as the browser
2) modify the line of code in error to something that works?

TIA,

Doug Heeren wrote:

You can simply do
  e[attributes[i].nodeName] = new Function(attributes[i].nodeValue);
no need to try to identify IE 8.

That woks perfectly. What is the difference between the two? On the surface
they appear to do the same.
Show quoteHide quote

Doug Heeren wrote:
Do they? No,
   e[e[attributes[i].nodeName] = ...
sets a property.
   e.setAttribute([attributes[i].nodeName], ...)
is supposed to set an attribute but is broken by design in IE before
version 8.

That makes sense. I appreciate this very much!

Show quoteHide quote

Is there a way to keep the StreamWriter open?
Visual Basic is Dead!
Detailsview updading issue
Basic question: returning @@IDENTITY from stored procedure...
Movenext and ASP.net
enum or static class
Document markup language version question
Skinning Question for checkboxes
winform security: strange error, where as I expected a redirect
Employee TimeSheet/Projects