I think there are still some IE8 issues. Now that a final is out,
they'll probably get resolved soon. I know kangax (at least) is
working on some of them and several have already been resolved in the
trunk version. Would you give the trunk version a go?
> Then that is a bug in IE 8.
It _may_ be. Half the point of readAttribute it that it "...cleans up
the horrible mess Internet Explorer makes when handling attributes"
and consequently it does a *lot* of processing around the getAttribute
call, including (in trunk) several IE8-specific branches. Always
possible that that code isn't handling something right. Equally, it's
entirely possible that there's a (new) bug in IE8. :-) I don't
currently have a machine I can load IE8 on to find out whether the
fault is in IE8's getAttribute or Prototype's readAttribute.
tj / crowder software / com
Independent Software Engineer, consulting services available
On Mar 21, 11:29 am, RobG <rg...@iinet.net.au> wrote:
> On Mar 20, 6:18 am, masterleep <bill-goo...@lipa.name> wrote:
> > OK, I found this particular one... if you call
> > input_elem.readAttribute('value');
> > on an input element, and the value is equal to the empty string, then
> > in IE8 the result is null.
> Then that is a bug in IE 8. readAttribute uses getAttribute, which
> returns a string in browsers that are compliant with the W3C DOM Core
> > On other browsers, the result is the empty
> > string.
> Which is compliant with the spec.
> An alternative is to use the DOM property for HTML attributes (i.e.
> inputElement.value) - what does that return (I don't have access to IE
> 8 at the moment)?
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 email@example.com
To unsubscribe from this group, send email to
For more options, visit this group at