Issue metadata
Sign in to add a comment
|
Permissions dialog doesn't distinguish between existing permissions vs new permissions
Reported by
t...@agilebits.com,
Apr 10 2017
|
||||||||||||||||||||||||
Issue description
Chrome Version : <Copy from: '57.0.2987.133'>
OS Version: OS X 10.12.0
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: OK
Firefox 4.x: OK
IE 7/8/9: OK
What steps will reproduce the problem?
1Password's browser extension had a new permission that it needed to ask for today. GC (reasonably!) disabled it until people gave permission.
However, people were greatly confused by the wording of the permission, which did not indicate which permissions were "old" and which one was "new" which led to people being concerned that we were asking for a lot more than we were.
What is the expected result?
It would be ideal if the new permission was highlighted, listed first, or otherwise made clear. Other, existing permissions, could either be left off or sectioned off in a way that makes it more clear.
What happens instead of that?
All permissions are listed together, making it impossible to tell what are new and what are old.
Please provide any additional information below. Attach a screenshot if possible.
,
Apr 11 2017
,
Apr 11 2017
Tested in chrome # 57.0.2987.113 and Canary #59.0.3068.1 on Mac 10.12.3.Unable to connect the password extensions and Please find the screen shots for your reference. @Reporter: Could you please let me know if i have missed anything and if possible,Please create new profile and Re-check once in latest canary #59.0.3068.1 and let us know the observations and provide the specific extension URL of the issue which would help us to triage the issue further. Thanks in Advance.
,
Apr 11 2017
This doesn't need feedback. The report is clear.
,
Apr 14 2017
ccing catmullings@ who was looking into updated permissions dialog.
,
Apr 14 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rsesek@chromium.org
, Apr 11 2017Status: Untriaged (was: Unconfirmed)