Something I forgot to add: using the .identify() method on the form
avoids this problem entirely.

On Feb 12, 12:37 pm, Doctuh <[EMAIL PROTECTED]> wrote:
> My first post. This is to document a tricky thing I found while using
> Element.readAttribute() on a form. This post is to help the next
> person looking for an answer on it.
>
> ex:
>
> <form id="foo">
>  <input type="hidden" name="id' value="bar" />
> </form>
>
> If you have a form with a hidden form element named 'id', and you try
> to use readAttribute() on the form you will get two different
> responses:
>
> IE gives you an Object (the input object named 'id')
> Firefox gives you 'foo'.
>
> IE will give you 'foo' is there is not a overriding form element.
>
> I did not expect this, thinking that readAttribute would be
> normalizing these behaviors, but IE sigh.
> This tied me up for a little while.  Thanks to jdalton and tobie on
> FreeNode for the help.
>
> -----
>
> Internet Explorer IE Firefox FF Element.readAttribute()
> readAttribute() String [object]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to