Re: Clarification of isDisplayed behaviour

Thanks.
So my understanding now is: the click itself would not be the test. I
would test for the expected outcome of the click.
The click was possible and succeeded, but webdriver does not know what
happened after that. Let the browser handle the click and capture
events as it would.

This makes me wonder why interactable needs to be defined at all. If
an element was found, interactions may be attempted on it.

On 20 September 2013 20:45, David Burns <dburns@mozilla.com> wrote:
> Paul,
>
> At the last face to face we did discuss this issue[1]. We left that meeting
> saying that we need to define interactable vs visible. The link in your
> example might not be clickable but I can tab and press enter. There was talk
> that we could error if we saw an element above another element but then what
> if someone has intentionally allowed events to pass through. I can't
> remember where we got with that.
>
> I have raised a bug[2] so we can keep track of it.
>
> David
>
>
> [1] http://www.w3.org/2013/06/13-testing-minutes.html#item03
> [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23309
>
>
> On 20/09/2013 15:46, Paul Money wrote:
>>
>> <a id="link" href="#">link</a>
>> <div style="background: black; width: 100%; height: 100%; position:
>> absolute; top:0; left:0;"></div>
>
>

Received on Friday, 20 September 2013 22:02:36 UTC