w3c / w3c/webdriver

Define the syntax of browserVersion?

Open
#1,898 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

New Session
Dominant language
HTML
Stars
718
Forks
228
PR merge metrics
No merged PRs in 30d

Description

c.f. https://w3c.github.io/webdriver/#:~:text=%22browserVersion%22,-Compare%20value%20to, which says:

Compare value to the "browserVersion" entry in matched capabilities using an implementation-defined comparison algorithm. The comparison is to accept a value that places constraints on the version using the "<", "<=", ">", and ">=" operators.

And the note below:

Version comparison is left as an implementation detail since each user agent will likely have conflicting methods of encoding the user agent version, and standardizing these schemes is beyond the scope of this standard.

While I get we don't want to define the actual semantics of the comparison operators, we should define what the syntax of the browserVersion capability is itself.

Like, is browserVersion expected to take values like >=1.0.0? Can you combine multiple comparisons?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked WebDriver specification section on the browserVersion capability and compare its stated comparison behavior with the questions in this issue. Done means the specification defines the capability's value syntax, including whether values such as >=1.0.0 and combined comparisons are allowed, without defining the comparison semantics.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.