Issue metadata
Sign in to add a comment
|
☂ Revamp Page Actions and Permission UI (Project Jewelbox) |
||||||||||||||||||||||||
Issue descriptionWe want to get rid of page actions (the icons on the right of the omnibox) for a handful of reasons. - dominickn@ is the owner for scoping out the project. - lgarron@ will share the implementation with dominickn@ (details to be scoped out). - rolfe@ is tackling the design aspects. Gooogle Drive folder (currently Google-internal): https://drive.google.com/corp/drive/folders/0B1kg1oK-WfnucUlYZm9GamFQdkU
,
Apr 6 2016
I find myself using the JS blocked menu multiple times every day and it's not very user friendly, so I welcome this revamp.
,
Apr 6 2016
,
Apr 11 2016
dominickn@ has named this project "Jewelbox" ("making permission UI shine").
https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3AHotlist-Jewelbox&sort=status&colspec=ID+Status+Owner+Summary+Modified&x=m&y=releaseblock&cells=ids
,
Apr 11 2016
love the name (& image!)
,
Apr 12 2016
,
May 15 2016
I am curious as to the progress on this; I was just about to suggest modifying the Permissions UI to reflect the recent changes in Android (see attached).
,
May 16 2016
Making permission request UI more "app-like" is one of the driving goals of this work - particularly designing a page like the app permissions one for sites. With all the focus on progressive web apps, we need to focus on improving the Chrome-side UX to support them better. Modal permission requests is a potential option, but it will require careful thought for a number of reasons: - we don't want to introduce another free way for sites to put up a modal dialog - hence, there may be implications for web platform APIs, which requires a longer discussion process to settle (e.g. APIs would need a user gesture to call) - it's unclear whether we should also make desktop permission dialogs modal
,
May 16 2016
I threw together a mock-up showing a desktop permissions modal (see image 1). While it definitely demands the user's attention, it does come with some concerns about responsiveness. Considering issue #606349, it would have to be able to handle long URLs; maybe site owners could provide a read-friendly 'app name'. Some other thoughts: - combining permission requests into a single dialogue/modal could prevent abuse - a 'more info' link could take users to more fine-grained controls (similar to the middle screenshot in the Android image submitted previously) - website permissions UX and extension permissions UX should be consistent (see image 2) Regardless, I think it would worth testing a couple alternatives with focus groups.
,
May 17 2016
Thanks! These are definitely food for thought. We have API side challenges for coalescing permission requests together. However, we're definitely looking at improving the consistency of permissions UI across all surfaces - including extensions. Our first steps are probably to look at incremental improvements to what we have now (probably focusing on improving the existing bubbles), as larger revamps will take more time and discussion.
,
Jun 30 2016
,
Jul 27 2016
Issue 259102 has been merged into this issue.
,
Nov 30 2016
,
Mar 29 2017
Removing myself and adding maxwalker as your primary security/privacy design contact
,
Nov 10 2017
,
Feb 9 2018
Closing this one out. Any work in this area will take place on smaller bugs, and I most likely won't be involved due to team changes. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by lgar...@chromium.org
, Apr 6 2016