Provide more information on `element click intercepted` error
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
A common issue when automating with WebDriver is that other elements block access to a desired element to interact with. Some drivers, e.g. Chromedriver provide a somewhat useful message like:
element click intercepted: Element
<div class="cup-body" aria-label="Americano" data-test="Americano" data-cy="Americano" data-v-7a0f9f00="">...</div>is not clickable at point (376, 548). Other element would receive the click:<div class="pay-container" data-v-a32a8090="">...</div>
(Session info: chrome=104.0.5112.101)
It would be super helpful for frameworks if such an error could provide the element id of that element that has blocked access. It could allow framework authors to run a set of corrections, e.g. scrolling element to a different end of the viewport, in order to mitigate the problem.
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 the issue's description of the element click intercepted error and review how WebDriver error information currently represents the obstructing element. Done means the specification defines what identifier or information should be provided for that element so frameworks can act on it.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100