UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Steps to reproduce the problem:
When a user installs an extension, they are presented with a very coarse permission scheme.
Users should be able to make informed choices about more granular security models, similar to Android apps.
Chrome Extensions can update and implement new features that may change the user's browser behaviour in meaningful ways. User input is not required to authorize this new browser behaviour.
What is the expected behavior?
What went wrong?
- Extensions should have more granular permission scheme, similar to Android apps
- Extensions should request their updated permission model when they are updated automatically. This would allow the user to make informed choices about how their experience is changing.
Did this work before? N/A
Chrome version: 52.0.2743.116 Channel: stable
OS Version: OS X 10.11.6