Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebDriver: install command optional parameters #764

Open
chrmod opened this issue Feb 13, 2025 · 3 comments
Open

WebDriver: install command optional parameters #764

chrmod opened this issue Feb 13, 2025 · 3 comments
Labels
needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time

Comments

@chrmod
Copy link

chrmod commented Feb 13, 2025

Current specs for WebDriver BiDi and proposal for WebDriver Classic both provide a basic capability to install a web extension.

But each browser may support additional parameters, for example to:

  • Allow in Incognito/Private Window/InPrivate/Private Browsing (Chromium/Firefox/Safari)
  • Allow access to file URLs (Chromium)
  • Collect errors (Chromium)
  • Install temporarily (Firefox)
  • Allow automatic updates (Firefox)
  • Allow access to search page results (Opera)
  • Pin to toolbar (Opera)

Are there any other params that a WedDriver should support?

How can we allow optional browser specific parameters?

@github-actions github-actions bot added needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time labels Feb 13, 2025
@chrmod
Copy link
Author

chrmod commented Feb 13, 2025

Related to #19 (comment) and #760

@kiaraarose
Copy link
Contributor

This is something Safari would be supportive of, especially in the case of granting permissions for the extension. In our sync meetings for cross browser testing, we decided to grant all of the permissions defined in the manifest automatically, but we will definitely have tests where we'd want to test that extension doesn't have permission if it wasn't granted by the user. So adding a parameter to disable the auto grant when the extension is loaded would be nice.

@xeenon
Copy link
Collaborator

xeenon commented Feb 13, 2025

Install temporarily (Firefox)
Allow automatic updates (Firefox)

All installs should be temporary when using web driver — this should not be a vector for malware to install malicious extensions. (So these should not be an option.)

Any option that isn't supported by one browser can just be ignored by the other browsers or trigger an error if that makes sense. But we should agree on any common options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time
Projects
None yet
Development

No branches or pull requests

3 participants