Ok thank you! I was not aware that it's a known issue. On Mar 12, 2017 12:33 AM, "Titus Fortner" <[email protected]> wrote:
> This is a known issue with geckodriver. The w3c spec calls for being able > to specify one of three levels. The default is supposed to wait for > document ready status like other drivers, but currently it has only > implemented the'eager' setting. For now you need to wait for an element to > be present on the page brie continuing your tests. If clicking or acting on > an element with Watir 6+, it does this wait automatically. > > -- > -- > 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] > > --- > You received this message because you are subscribed to the Google Groups > "Watir General" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- 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] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
