Scrolling element into view for `Element Send Keys` is unclear
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
https://w3c.github.io/webdriver/webdriver-spec.html#element-send-keys
14.3 Element Send Keys
The Element Send Keys command scrolls into view the form control element and then sends the
provided keys to the element.
The scroll attempt should not only be done for form elements, but at least also for contenteditable elements. Further there are focusable elements like HTMLAnchorElement, which we might also want to bring into view if possible.
So maybe we can make use of the following step?
The Element Send Keys command scrolls into view the focusable element, and ...
Also it would be good to explain how to detect if an element is focusable. Simply by checking for the presence of the focus method on the element is not enough given that it is present even for HTMLElement.
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 Element Send Keys section in the linked WebDriver specification. Determine how scrolling should apply to contenteditable and other focusable elements, and how focusability should be defined beyond checking for a focus method. Done means the specification clearly identifies the scrolling target and provides an unambiguous focusability rule; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100