Sorry, didn't include the explanation of the issue.... what the onload event does is reinforce any frames loaded in the browser to occupy the whole window of the browser.
Eg: specific to the our app, when the test simulates user clicking the login button, this'll trigger the onload event that forces the login page to occupy the whole browser.
One way, to get around this is by logging in in a browser and run the test in other browser (somehow the session is reused by selenium). This is done in IE.
hth,
crue
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
_______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
