In mv3, the idea is to only have host_permissions and make them optional by default. This prevents vendors from deciding whether or not some host_permissions should be requested upon installation or only later in the process. And also prevents extension authors from telling the stores, browsers and users what host_permissions are needed for the core functionality and which ones are optional_host_permissions.
The proposal here is to add a new property in addition to host_permissions named optional_host_permissions allowing extension authors to define which host permissions are optional and which are mandatory for the core functionality. This would then allow some vendors to request the required host permissions upon installation, and allow other vendors to also treat the required host_permissions as being optional.
For example, Apple currently requests host permissions just after installation from the user. Yet the developer may not want to ask all host permissions right away upon installation.
One of the reasons for this proposal is the fact not all extensions act on websites / tabs, but need host permissions for functionality provided separately in an extension popup completely independent from browser tabs.
An issue in the chromium issue tracker can be found here:
https://bugs.chromium.org/p/chromium/issues/detail?id=1265064
Status
Apple Safari: in favor, not yet implemented.
Mozilla Firefox: in favor, not yet implemented.
Google Chrome: intend to support this, will work on it soon.
In mv3, the idea is to only have
host_permissionsand make them optional by default. This prevents vendors from deciding whether or not somehost_permissionsshould be requested upon installation or only later in the process. And also prevents extension authors from telling the stores, browsers and users whathost_permissionsare needed for the core functionality and which ones areoptional_host_permissions.The proposal here is to add a new property in addition to
host_permissionsnamedoptional_host_permissionsallowing extension authors to define which host permissions are optional and which are mandatory for the core functionality. This would then allow some vendors to request the required host permissions upon installation, and allow other vendors to also treat the requiredhost_permissionsas being optional.For example, Apple currently requests host permissions just after installation from the user. Yet the developer may not want to ask all host permissions right away upon installation.
One of the reasons for this proposal is the fact not all extensions act on websites / tabs, but need host permissions for functionality provided separately in an extension popup completely independent from browser tabs.
An issue in the chromium issue tracker can be found here:
https://bugs.chromium.org/p/chromium/issues/detail?id=1265064
Status
Apple Safari: in favor, not yet implemented.
Mozilla Firefox: in favor, not yet implemented.
Google Chrome: intend to support this, will work on it soon.