setWindowRect should be matched as a capability
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Nowhere does https://w3c.github.io/webdriver/#dfn-matching-capabilities match setWindowRect, so it effectively is ignored when passed as a capability (see: https://github.com/w3c/webdriver/issues/1792).
However, per @whimboo:
In Firefox we match that capability and fail if the value is not appropriate
I have not tested what other implementations do.
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 WebDriver specification's matching capabilities definition and the setWindowRect capability, then review the linked WebDriver issue 1792 and the referenced discussion. Done when the specification clearly defines whether and how setWindowRect is matched, consistently with the stated Firefox behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100