w3c / w3c/webdriver

Element can match multiple ifs under Element Click

Open
#1,106 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Element Click
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 the element’s center point is obscured by another element, an element click intercepted error is returned. If the element is outside the viewport, an element not interactable error is returned.

An element outside the viewport is obscured, therefore given there's nothing saying that you do these in order (indeed, it makes no sense to apply these sentences after the previous one!), so it's ambiguous as to what error should be returned.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with section 14.1, Element Click, in the linked WebDriver specification and read the surrounding interaction-error text. Determine how the obscured and out-of-viewport conditions should be ordered or distinguished, then update the normative wording so one unambiguous error is selected and review the resulting specification text.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.