Element Click does not do wait for element interactability.
Open
Nobody has claimed this yet.
bug
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with section 14.1 Element Click in the WebDriver specification and compare its interactability handling with the other Element Interaction commands. Determine the expected wait behavior for an element whose container is not in view, and update the specification so Element Click consistently checks interactability before interacting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100