Open GoogleCodeExporter opened 8 years ago
Original comment by phil.boo...@gtempaccount.com
on 28 Sep 2009 at 2:16
I can see two issues here.
Firstly, the driver file is using verifyVisible where waitForVisible would be
more
appropriate, to allow the UI to finish updating before verification is made.
Secondly, it also looks like issue 525 ("Dispatch of DOMActivate from trigger
elements is not reliable") may be having some effect. Extra messages, caused by
the
double-activation of the trigger in Safari, appear to prevent Selenium from
progressing at one point.
So, I'm marking issue 525 as a blocker on this one, and will look to get that
resolved first.
Original comment by phil.boo...@gtempaccount.com
on 28 Sep 2009 at 2:54
Original comment by phil.boo...@gtempaccount.com
on 1 Oct 2009 at 4:11
Original comment by phil.boo...@gtempaccount.com
on 5 Oct 2009 at 9:48
Original comment by phil.boo...@gtempaccount.com
on 21 Oct 2009 at 9:36
Original issue reported on code.google.com by
phil.boo...@gtempaccount.com
on 22 Sep 2009 at 3:19