Capability defaults are split between Match Capabilities and New Session
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Currently upon read-through of the spec defaults for capabilities are in two different sections. There is an initial list mentioned in Match Capabilities which defines some defaults for comparison although they aren't called out as defaults they are used for comparison to validate.
Then in New Session there are defaults specified for pageLoadStrategy and timeouts.
These should be consolidated in some way (I'd argue the ones in New Session should be moved into Match Capabilities).
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
Read the Match Capabilities and New Session sections in the linked WebDriver specification, comparing how capability defaults are defined and used. Consolidate the defaults into one section, following the issue's suggested direction, and confirm that the specification has one clear source for these defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100