Re: Implicit Wait

I'm going to be totting up the +1s. Just to be clear, you're:

+1 to implicit waits
-1 to waiting for interactability for "Do What I Mean" commands.

FYI, the Selenium Firefox driver _does_ wait for interactability. It's not
particularly obvious, but check the "preconditions
<https://github.com/SeleniumHQ/selenium/blob/master/javascript/firefox-driver/js/wrappedElement.js#L91>"
property of each method. I guess you're talking about geckodriver? Does
that change your vote?

Simon

On Mon, Oct 31, 2016 at 1:12 PM, David Burns <dburns@mozilla.com> wrote:

> +1 to having implicit waits. There are about 7 PHP drivers and a billion
> JS drivers which might be using this and it's not going to be easy updating
> them.
>
> Looking at FirefoxDriver, and going on what Jim said, we have 2 drivers
> that don't wait for interactable from the Selenium project. With this in
> mind, I vote +1 on keeping Selenium's existing behaviour for the majority
> of drivers which is to *NOT* wait for interactability.
>
> David
>
> On 29 October 2016 at 16:02, Andreas Tolfsen <ato@mozilla.com> wrote:
>
>> Simon Stewart <simon.m.stewart@gmail.com> writes:
>>
>> > […] and +1 for retaining selenium's existing behaviour of using the
>> > same time out for waiting for interactability for "do what I mean"
>> > interaction commands.
>>
>> For clarity, as Jim pointed out, not all Selenium implementations do
>> this.
>>
>
>