Is anyone else suddenly discovering they have difficulty with scripts
using a click immediately following onmouseover / hover type events in
firefox 8? It's as if FF is reporting the true mouse position to the
app immediately after I've done something like a click/mouseover event/
hover and thus the client side code is un-rendering the control. as
a result I get exceptions for "Element not currently visible"
My particular situationis that II have some fancy pulldown menus in
our app that are a bit of a challenge to automate since they are very
event driven (pulling up the pop-down menus when you mouse over or
click on the menu name) I'd been working with them by using either
an onmouseover or a click to make the menu appear, followed by
clicking the (now visible) link for the menu item I want. That was
working in FF7. Now with FF8 the item shows up ever so briefly (on a
click) and then vanishes, or never even shows up at all (as if the
event was never fired)
With FF7 I was able to work with them by using code along these lines
$browser.ul(:id => 'secondary_nav').li(:class => 'has_child_items
selected first').click
$browser.link(:text, 'Create New').click
(the menu bar is a UL (unordered list), and each LI element is one of
the top level menus. The click/mouseover on that item causes the
'pulldown' menu to appear. Thus allowing to click on the menu item
(in the form of a link) that is desired.)
In FF7 that code works just fine, in FF8 the sub-menu is not visible
(or not vis long enough) and generates the element not visible
message.
Is there perhaps some way in watir-webdriver to directly position the
actual mouse cursor over an object in the DOM so that we get a
'genuine' hover response from the browser?
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
[email protected]
http://groups.google.com/group/watir-general
[email protected]
