platformName/browserName case sensitivity
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Currently platformName/browserName have to be passed in ASCII lowercase to match (they're lowercased before comparison); some quick testing makes it seem like chromedriver and geckodriver do have this behaviour, but safaridriver does not.
Searching on GitHub suggests there's a reasonably large amount of usage, of "Android" and "iOS" especially (and the latter makes me wonder if chromedriver and/or geckodriver do something different for Android?). That said, even Windows, Linux, macOS see common usage — even on the Selenium docs (cc @shs96c). That said, I wonder if Selenium is lowercasing them before it gets beyond it?
I'm slightly hesitant about changing behaviour of iOS here, but probably needs more testing to check what various implementations do when given an uppercase platformName/browserName — does it simply never reach the wire protocol?
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 linked WebDriver specification sections on ASCII lowercasing and capability matching, then compare uppercase platformName and browserName behavior across the referenced drivers. Record whether the behavior is consistent and determine whether the specification needs a clarified requirement or no change.
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
- Needs clarification
- Newbie friendliness
- 25/100