When an mv3 extension is force_installed via policy, users should not be able to change host permissions
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: mkaply, Unassigned)
References
(Blocks 1 open bug)
Details
In Chrome and Edge, if an extension is force_installed, users cannot change the host permissions.
See:
https://github.com/mozilla/policy-templates/discussions/1111
|
||
Comment 1•3 months ago
|
||
Our permissions system is a bit different from Chromium, I'm not sure we want this to be the default behavior for all extensions, maybe have a separate opt-in policy?
And in any case, if we ever support this, we'd need to have it clear in the UI that permissions can't be revoked because the extension is controlled by the administrator.
|
Reporter | |
Comment 2•3 months ago
|
||
I'm not sure we want this to be the default behavior for all extensions, maybe have a separate opt-in policy?
I thought about that, but it seemed redundant since it only happens if the extension is installed via policy anyway.
depending on the usecase, it might be that it only works for admin only extensions.
And in any case, if we ever support this, we'd need to have it clear in the UI that permissions can't be revoked because the extension is controlled by the administrator.
Definitely.
Description
•