w3c / w3c/webdriver

WebExtensions should expose Capabilities they support

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

Nobody has claimed this yet.

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

Description

New Session currently fails to match extension capabilities that are unrecognised. However, a WebExtension could conceivably provide new WebDriver endpoints, and new capability names. There should be support for these.

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 by reading the WebDriver specification's New Session processing and its capability-matching rules. The issue names no file or test entry point; done should mean that WebExtensions can expose supported WebDriver endpoints and new capability names without those capabilities being rejected as unrecognised.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.