If I automate mouse actions using Selenium2/Webdriver in combination with Firefox 12, I can easily get the "mouse" to move to and hover over a context menu so the sub-menus are seen. However, if I have the real mouse resting outside of the active window running the test, there's a 99% chance when the hover action occurs, the context menu will flash quickly and disappear as if the mouse had moved. This causes the next step in the test to fail since the web element is no longer visible.
Once in a blue moon the test will run fine if the mouse is outside of the window. That's definitely a rare instance. If the real mouse is resting anywhere inside of the active window running the test, the hover action and test will run without issue 100% of the time.
Has anyone experienced this behavior or is it a known issue of Selenium2/Webdriver and Firefox? If you have experienced this, although it doesn't seem likely there could be a workaround, have you found a way to counteract this behavior?
It's a pain to have to wait for a test to run if it contains a hover command instead of letting it go in the background while I continue working on something else.