WebExtensions/Permissions: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This page covers permissions for [[WebExtensions|WebExtensions]] in Firefox. There are a few main parts: required permissions, optional permissions and the permissions API. | This page covers permissions for [[WebExtensions|WebExtensions]] in Firefox. There are a few main parts: required permissions, optional permissions and the permissions API. | ||
'''Initial [https://docs.google.com/document/d/1jZQUeIfelisRXBMaTuPTo2hXiIcPT3IpdYwQXDpzEMI/edit product requirements document].''' | |||
== Required permissions == | == Required permissions == | ||
This is the biggest class and it covers prompting a user when they install an add-on. If they upgrade an add-on and the permissions change then they will also be prompted with a warning for the upgrades. | This is the biggest class and it covers prompting a user when they install an add-on. If they upgrade an add-on and the permissions change then they will also be prompted with a warning for the upgrades. | ||
'''When''': aiming for Firefox 53. | '''When''': aiming for Firefox 53. | ||
| Line 20: | Line 20: | ||
* changes to legacy extension types | * changes to legacy extension types | ||
Tracking bug | Tracking bug: {{Bugzilla|1308292}} | ||
<bugzilla> | <bugzilla> | ||
| Line 38: | Line 38: | ||
Optional permissions are currently in the planning stage and will land after required permissions. This is because the majority of extensions on the Chrome store have a required permission (around 90%). Where as only about 8% have an optional permission. | Optional permissions are currently in the planning stage and will land after required permissions. This is because the majority of extensions on the Chrome store have a required permission (around 90%). Where as only about 8% have an optional permission. | ||
Tracking bug | '''When''': aiming for Firefox 54. | ||
Tracking bug: {{Bugzilla|1197420}} | |||
<bugzilla> | <bugzilla> | ||
| Line 51: | Line 53: | ||
The main UX flow for this is [https://www.figma.com/file/HrLiKUwoLQZsIUIVBKM8Wnnu/Install-Flow-showing-Permissions on Figma]. However at the time of writing there a few divergences from the user interface, noted above. | The main UX flow for this is [https://www.figma.com/file/HrLiKUwoLQZsIUIVBKM8Wnnu/Install-Flow-showing-Permissions on Figma]. However at the time of writing there a few divergences from the user interface, noted above. | ||
Revision as of 00:09, 10 November 2016
This page covers permissions for WebExtensions in Firefox. There are a few main parts: required permissions, optional permissions and the permissions API.
Initial product requirements document.
Required permissions
This is the biggest class and it covers prompting a user when they install an add-on. If they upgrade an add-on and the permissions change then they will also be prompted with a warning for the upgrades.
When: aiming for Firefox 53.
Scenarios being looked at include:
- installing a WebExtension from a third party site
- installing a WebExtension from AMO or the disco pane
- installing a WebExtension temporarily through about:debugging (no permissions should be shown)
- installing a WebExtension through about:addons
- have a WebExtension be side loaded
- have a WebExtension be upgraded
Not covered:
- changes to legacy extension types
Tracking bug: 1308292
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
UX
The main UX flow for this is on Figma. However at the time of writing there a few divergences from the user interface, noted above.
Optional permissions and associated permissions API
Optional permissions are currently in the planning stage and will land after required permissions. This is because the majority of extensions on the Chrome store have a required permission (around 90%). Where as only about 8% have an optional permission.
When: aiming for Firefox 54.
Tracking bug: 1197420
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
UX
The main UX flow for this is on Figma. However at the time of writing there a few divergences from the user interface, noted above.