Element Click does not do wait for element interactability.

[AutomatedTester]

In chapter 14. Element Interaction, section 14.1 Element Click:

If element’s container is still not in view, return error with error code element not interactable.

The other Element Interaction commands check if an element is interactable before interacting with it

[andreastt]

Element Click does check if the element is interactable:

5. If element’s container is still not in view, return error with error code element not interactable.

6. If element’s container is obscured by another element, return error with error code element click intercepted.

[AutomatedTester]

@andreastt

I had put the wrong title, I have updated. The specification does not do a wait for interactable before carrying on. We have this in the other element interaction commands but not click. We are also not in line with some of the legacy drivers from the Selenium project

[Rajagopalan-M]

@AutomatedTester Hi, Is this updated ? Will this facility comes in geckodriver in future?

[AutomatedTester]

@Rajagopalan-M when the bug here is done then other drivers can implement it and not before

[Rajagopalan-M]

@AutomatedTester No, I did not understand, What do you mean by other drivers can implement? Which driver?

[AutomatedTester]

@Rajagopalan-M this bug is to make sure we specify how to do it. When its done then we can raise a bug against geckodriver to make sure their is code for it

[Rajagopalan-M]

@AutomatedTester Okay, thank you.