1229230 - Define how Add-on Permissions help users (and how they may be surfaced to them)

Status: RESOLVED INVALID

(WebExtensions :: Untriaged, defect, P3)

Description

[Markus Jaritz [:designakt] (UX)]

With WebExtensions we will know what permissions an add-on requests to use.
This can be used to surface these permissions to users if necessary. 

Can each permission be granted individually?
Do add-ons have to work with every combination of allowed permissions?
How do we surface updates that extend permissions?
What happens if users refuse updates that extend permissions? 
Will they be opted out of updates?
If users have to accept any permission, should we only inform instead of ask? (see Chrome)

see https://twitter.com/phlsa/status/670282504725798912

If we give the user the power to decide which permissions to allow, and which not, what does this mean for add-on developers. Can this lead to considerate usage of add-ons or will every add-on request every permission so to never have to ask again on possible future updates that would extend functionality...

How does using permissions make add-on usage any safer?

Currently this is a topic with many Questions that need to be asked and answered.

Comment 1

[:shell escalante]

Hi markus - do you have next steps for this? / priority against other UX work?

Comment 2

[Markus Jaritz [:designakt] (UX)]

I see improving WebExtension as the next step. Right after we have established a solid discovery for add-ons.

Comment 3

[Andy McKay]

I think this bug is being covered in other places, primarily in github and bug 1308292 and doesn't serve a purpose. If you disagree markus please let me know.