The MooTools Object.each() method pointed out by Dimitar Christoff is the right way.

Additionnaly you may want to have a look at this article : http://blog.tuenti.com/dev/top-13-javascript-mistakes/

Your mistake was listed in first.

i will apologize again, i keep saying “associative arrays” when yes, they are objects

about hasOwnProperty, i don’t figure out how it works better than my solution, in what change to check:
if(var==”$family”) than hasOwnProperty(var) ?

thanks for your corrections anyway

Regards.

http://www.quirksmode.org/js/associative.html
http://stackoverflow.com/questions/3831181/javascript-associative-array http://stackoverflow.com/questions/2546798/from-a-language-design-perspective-if-javascript-objects-are-simply-associative and

your $family solution instead of hasOwnProperty really made me smile. god kills kittens when your loops run

i apologize if i explained it wrong but was not my intention to blame the framework. what you say about objects and how it works, i already know it when i found the “glitch”, to say it in some way, my post try to clarify that the function do not will process associative arrays, maybe is something obvious for you, was not for me and there is no warning about that on mootools docs also.
when i say that maybe was a glitch or a bug, why maybe the devs wanted that the function will work anyway with associative arrays and is not, just for that.

about that the for will process all the object, you just need to stop processing the objects after you found the key $family and that will solve it

thanks for the suggestion and opinion about the subject anyway

Regards,
Shadow.

myArray.length in your example will be 0 (which is native javascript) which means the .each iteration will not work. array keys are meant to be numeric indices. If you want associative arrays functionality, you are advised to use objects instead. look at http://jsfiddle.net/dimitar/458wu/

And finally, mootools is prototypical. This means the Array prototype inherits all the array methods that mootools defines. In your example, it will loop through the local array properties but also through the methods defined by mootools like .each, getRandom etc etc – because you don’t do a .hasOwnProperty() check. Google on ‘javascript array hasOwnProperty’ and read up.

Posts like that blaming the framework without checking your javascript first are hardly constructive. Good luck

now, for the first popup, you can use the waitForPopup function, passing the id of the popup to wait for. then you will execute the clickAndWait function to click on the OK button. after that, you need a new waitForPopup action for the second one. the complicated part comes with the java applet, as the ok button is there and i don’t think selenium IDE could make a click inside the applet. in this case, you can run a runScript function, to se or run some js function, and send some parameter to the applet to make the click on the OK and continue the login process.

i hope it helps.