On May 8, 12:56 pm, "J.R." <[email protected]> wrote: [...] > Well, I was having a mysterious problem with indexOf returning a wrong > value. After testing with FF4, I decided to go back to Chrome's console > (Ctrl + Shift + J) and typed > > [0, false, 15].indexOf(false); // console returned 0 instead of 1. > > Now, I've just updated my Google Chrome to 11.0.696.65 version and ta-da... > my code began to work correctly. It's really weird because I didn't change > anything in my code. It seems to me that the older version (prior > to 11.0.696.65) had that bug in Array.Prototype.indexOf(). Seems like a bug > also discovered by the Chrome team and rapidly corrected.
And, because it automatically updates whenever it wants, it is impossible to go back to the earlier version to check. One reason I don't use Chrome - I hate applications that don't give me a choice about updates. -- Rob -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
