That is the case which all the browsers returned the first matched element, and the firefox because I call the getElementById has disturb his understanding on the DOM structure and the second call return me the second matched, and ie opera safari and ff3.0a5 won't be disturbed by this code, so it must be a bug of the firefox2.0, I know this is wrong html, but with the wrong html all the browsers return the first matched, and in ff2.0 my code has disturb it, and return the second matched, so I think this is a bug, and ff3.0 fix it.
On Jun 18, 11:53 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > On 6/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Not only IE and Opera, of course firefox, look at this code > > Dude, I told you ... you have 2 elements with the same ID ... and you want > us to fix it in the framework?? > > Can't do, sorry. You'll just have to learn to code better. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" 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/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
