Hi Steve, its the iteration of the same array that is different, note the different output of my script, maybe its not mootools bug, but its a bug created as a result of a different implementation of JS foreach (FF vs IE).
Fabio, would love for this to be solved in Mootools, I will open a ticket. Cheers -- Roman 2009/12/14 Fábio M. Costa <[email protected]> > if $each is throwing an error beacuse of this, than this is a bug. But i > think that 1.3 still has this fixed. > The best thing you could do is create a ticket at lighthouse about it. > > https://mootools.lighthouseapp.com/projects/2706-mootools/overview > > -- > Fábio Miranda Costa > Solucione Sistemas > Engenheiro de interfaces > > > > On Mon, Dec 14, 2009 at 10:38 AM, Steve Onnis <[email protected]>wrote: > >> this is not a bug. javascript arrays start from zero , not one. >> >> example, >> >> foo = [] >> foo[100] = "foo" >> >> this array now has 100 items in it, and items 0 to 98 are null or >> undefined. IE craps out with this, firefox tends to be a little more >> graceful and tell you its "undefined" >> >> As you can see in your example, the array has 5 items in it. Just because >> you start from one doesnt mean the "each" will start from one. >> >> ------------------------------ >> *From:* Roman Land [mailto:[email protected]] >> *Sent:* Monday, 14 December 2009 11:14 PM >> *To:* [email protected] >> *Subject:* [Moo] Found a very annoying bug.. >> >> Hi, >> >> It seems that if an array does not have an element in position 0, $each in >> IE will still try to iterate over it, simple demonstration: >> http://mooshell.net/ehTsR/ >> >> When trying to access the item itself, IE will error out and stop.. >> >> A bug? >> >> Thanks! >> -- Roman >> >> -- >> --- >> "Make everything as simple as possible, but not simpler." >> >> - Albert Einstein >> >> > -- --- "Make everything as simple as possible, but not simpler." - Albert Einstein
