Re-design permissions screen to support optional permissions
Categories
(Fenix :: WebExtensions, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: amejia, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
permission_screen.png
In this screen:
We will have three type of permissions "Required" , "Optional" and "host permissions".
"Required" are not updated able.
"Optional" can be removed or granted a run-time
"Host" they can be allow all or site specific.
|
||
Comment 1•2 years ago
|
||
Desktop side was handled in bug 1745820 and bug 1777354.
Although the summary here frames this as a MV3-only task, it's also relevant to MV2.
The main difference between MV2 and MV3 in the context of permissions is that MV3 makes all host permissions optional, whereas in MV2 an extension can have required host permissions.
In MV2 (and MV3), the extension API to request optional permissions on demand is permissions.request(). The GeckoView side of it has been implemented in bug 1601420. But the A-C/Fenix side still needs to be implemented, in bug 1810047.
The bug here would be the user-facing interface to control the permissions.
|
Reporter | |
Comment 2•2 years ago
|
||
Thanks Rob for all the context!
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
||
Updated•2 years ago
|
|
||
Updated•2 years ago
|
Description
•