WebExtensions/Permissions

From MozillaWiki
Jump to: navigation, search

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.

Status

Update January 2017: Mostly landed in Nightly and should be on by default in Firefox 54.

You can try it out until its on by default by creating the preference: extensions.webextPermissionPrompts as a boolean set to true. Then install a WebExtension. Here are some examples.

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

Full Query
ID Priority Status Summary
1444294 P5 NEW Implement permissions API events

1 Total; 1 Open (100%); 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.