Add optional_host_permissions in mv3
Categories
(WebExtensions :: Compatibility, enhancement, P3)
Tracking
(firefox128 fixed)
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: zombie, Assigned: zombie)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete, Whiteboard: [addons-jira] [wecg])
Attachments
(2 files)
As discussed in https://github.com/w3c/webextensions/issues/119#issuecomment-965799707
There's still a need to separate some host permissions as "wanted" and some as "optional", and treat them differently in the UI. That's why, contrary to Chrome, when I was adding host_permissions
support, I kept origins allowed in optional_permissions
in mv3.
After that, the issue was raised in the WECG and we agreed on the optional_host_permissions
manifest key to solve for this use case.
When we add that, we can deprecate (warn about) using origins in optional_permissions
, but it's not a priority to drop it, it's not a costly thing keep supporting for us.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•3 years ago
|
||
During today's WECG meeting (minutes tentatively under review at https://github.com/w3c/webextensions/pull/239), we agreed that it would make sense to drop support for host permissions in the optional_permissions section, in favor of optional_host_permissions. Safari and Chrome 102+ support optional_host_permissions now, and the cross-browser consensus is to only support host permissions in optional_host_permissions.
Comment 2•2 years ago
|
||
In Firefox Nightly 109.0a1 (2022-11-14) (64 bits), If you Load this Temporary Add-on...
{
"manifest_version": 3,
"name": "Test case",
"version": "1.0.0",
"host_permissions": ["https://fr.wikipedia.org/"]
}
Go to Manage Your Extensions > Test case > Permissions. The permission to Wikipedia is in Optional permissions for added functionality. It must be in Required permissions for core functionality.
Comment 3•2 years ago
|
||
Hopefully this is implemented soon, This could help alleviate the bug #1851083 where an extension with activeTab
in order to reduce the usage of to broad permissions, gets a blue badge over the action on every website.
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Although the functionality is independent, Tom mentioned that the implementation would be easier after landing the changes from bug 1889402, so I'm marking that one as a dependency of this bug.
Assignee | ||
Comment 6•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 7•1 year ago
|
||
Depends on D210397
Comment 9•1 year ago
|
||
bugherder |
Comment 10•1 year ago
|
||
(linking bug 1769184 for visibility of the fact that we have to land changes with skips for condprof followed by removing the skips later)
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Comment 13•1 year ago
|
||
Draft MDN content changes are ready for review:
- MDN content Add optional_host_permissions docs #33811
- BCD Add optional_host_permissions #23177
Description
•