Open GoogleCodeExporter opened 8 years ago
Thanks to Simon Stewart (of Selenium and WebDriver fame) who suggested trying
older versions of Firefox, I've discovered the current issues seem to be
related to Firefox 3.6.x (I've seen the problem with 3.6.10 and 3.6.12). When I
use 3.0.19 (the last version of Firefox 3.0) and 3.5.10 (one of the later
releases of 3.5) the keyboard handling behaviour works as expected.
I've investigating the differences, and that the first test (tabbing into a
hidden iframe) often fails with a Stale Element Exception. This occurs when the
code recurses into itself to tab through the iframe, after the first Tab is
issued. I'll continue to investigate the problem and try to find a robust fix.
Julian 11 Nov 2010
Original comment by julianharty
on 11 Nov 2010 at 8:40
Any news on this? I'm testing a GWT app with Firefox 5 and I'm often running
into this exception. Thanks.
Original comment by hanrisel...@gmail.com
on 10 Aug 2011 at 10:40
I haven't looked at this for a while, however now you've provided some impetus
to do so I shall, probably later this week. Thanks for the prod.
Which OS are you running the tests on? (Where is Firefox running?)
Julian
Original comment by julianharty
on 10 Aug 2011 at 3:14
A quick update:
Only 1 test now fails, the one with the hidden iframe that doesn't have an
explicit tabindex="-1" called
testGwtHistoryIframeIncludedWhenTabbingAndNoTabindexSet I have refined the
algorithms to detect problems related to native events not behaving corrently.
The current problem affects each of the browsers I've tests (Firefox, Chrome
and InternetExplorer). I'm continuing to investigate the problem with the
Selenium / WebDriver team.
Original comment by julianharty
on 6 Sep 2011 at 5:29
Original issue reported on code.google.com by
julianharty
on 9 Nov 2010 at 5:39