Add guidelines as to when commands should be in WebDriver v. other specs
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Based on a discussion within the WPT core team, it would be good to have some guidance as to when things belong in the WebDriver spec versus when they should be defined in other specs. (This discussion was originally about #1695, but this is a more general question.)
@jgraham's suggestion was anything that deeply ties into other specs should be defined in those other specs, but of course in theory this also applies to things like the WebDriver navigation commands.
It would be good to have some documentation for contributors as to whether they should add a WebDriver endpoint to WebDriver v. put it in another spec.
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 by reviewing the WPT core team discussion referenced in the issue, then compare the WebDriver specification with the other specifications that define navigation and related behavior. Done means contributors have clear guidance on when to add a WebDriver endpoint and when to define behavior elsewhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100