dev_permissions
/ self_permissions
key in manifest
#688
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
topic: permissions
Summary
As an extension developer, we sometimes run into cases where the permissions that help with the process of development, testing, and internal observability are not necessarily useful to our end users (and additionally would trigger negative warnings at installation). The issue is heightened by the fact some of these tooling-centric permissions, such as
debugger
anddevtools
, are not able to be specified as optional in the manifest, presumably as these are high-powered APIs and user security is a critical consideration.I propose a
dev_permissions
orself_permissions
key in the manifest schema which would grant permissions that apply only to unpacked installations, thus being inapplicable to builds uploaded to and installed from the web stores. A parallel but not identical concept is Node'sdevDependencies
which specifies different instructions to the npm installer based on the environment in which it's being run.Workaround
The only current workarounds I'm aware of are: either maintaining a separate manifest file entirely for development vs web store builds, or modifying the manifest file permissions key as a part of extension build and release.
The text was updated successfully, but these errors were encountered: