An effort to make it clear to users the ways in which extensions change the behavior of their browser.
Note from andym: I hate giving projects code names, but we couldn't think of a good summary for this project that didn't involve being confused with every other permissions and objects project. So we have Jazz and that seems cool since we have Disco Pane.
Let's find a way to show users of extensions what the extensions do to their browser after they are installed. This includes, but is not limited to:
- showing a user the permissions granted by a user to the add-on
- allow a user to revoke permissions (both optional and required) from the add-on
- showing a user which command combinations an add-on requests
- allowing a user to change the command combinations an add-on requests
- show what collisions in APIs add-ons might represent
- allowing the user to override or change key functionality such as: search engines, home page, new tab pages
- we need this for *all* prefs that are accessible via the UI and also controllable by WebExtensions
- we need to consider whether a user should be able to specify a value for a preference, and have that block WebExtensions from overriding the preference, and if so, how would that work/what would it look like
What's been done so far:
Tracking bug is 1342584.
13 Total; 13 Open (100%); 0 Resolved (0%); 0 Verified (0%);
These may or may not be visible to everyone:
The current mocks can be found at https://mozilla.invisionapp.com/share/6HCITJKP8.