Molybdenum doesn't work correctly in Firefox3
Error case:
One of the commands provoking this problem is the command waitForPopUp.
Potentially all commands dealing with popups are affected.
The command is failing and the error stacktrace in the Selenium console is incomplete. But what can be seen is something like that:
Therefore the problem is named XPCJOW445 by us.
Background:
Bugzilla entry
Description of the new FF3 Wrapper object
What todo?
At the moment it is not clear if this is an expected behavior of Firefox3 and if, how to deal with it. We will watch the Bugzilla entry above for a possible answer.
Warning
The bug is potentially affecting window and DOM access from chrome scope for all extensions. As you can see, firebug has trouble with that phenomena as well. Even SeleniumIDE is not working correctly here.
A special incarnation of this problem can be found if selenium-core is used and the AUT is loaded from filesystem. If the selenium-core testsuite is executed from filesystem and the refresh test is executed, all tests will fail from now on.
Thoughts
The root cause of the problem could be the fact, that popups are opened in the AUT domain scope and enriched with some properties like the selenium unique id. Exactly this props cannot be accessed afterwards from chrome scope. Access is producing the error above.
Might be, it is possible to bring all script objects and properties in the chrome scope. This could be done by sending a custom event to the Molybdenum chrome window and dealing inside the event routine with all object modifications.
Additionally, we can replace the cross browser windows ready state and popup detection logic of selenium with some XPC functionality like using WindowsWatcher.
