Hey Josh,
Josh on Rails a écrit :
> More: Looking at the getElementsByClassName declaration in
> prototype.js, I'd guess this is really a problem with $A or
> getElementsByTagName, but that's as far as I got.
Hey there. Yes, this is IE only, and the reason is that IE provides a
"dot-id" child access:
x.childIdOrName
provides access to a child node of x whose id (or name, a more general
issue with IE) is "childIdOrName").
The problem is that IE does that BEFORE resolving property names. So
when you have a HTMLCollection (as is returned by getElementsByTagName)
with a item(...) method and a lenth property (as per DOM Level 2 HTML),
and one of the items is id'd or named "item" or "length", IE freaks out.
Just another consequence of IE's shabby DOM implementation and standards
compliance.
The solution lies indeed where you put it: either change the field's
name (and ID, if need be), or use the scope feature with the parent option.
This post just so you get what the actual problem is...
--
Christophe Porteneuve aka TDD
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
