Chrome OS wishlist: "Settings" should be listed as an app in the launcher, like all other OS
Reported by
alan.chr...@gmail.com,
Jun 1 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7978.74.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.103 Safari/537.36 Platform: 7978.74.0 (Official Build) stable-channel candy Steps to reproduce the problem: 1. Chrome OS 2. Open Launcher (search button on keyboard, or onscreen on the left of Shelf) 3. Type "settings" What is the expected behavior? Settings app appears, so that I am able to easily open Settings app using the keyboard, like any other app. What went wrong? Settings is not listed Did this work before? No Chrome version: 50.0.2661.103 Channel: stable OS Version: 7978.74.0 Flash Version: Shockwave Flash 21.0 r0 This behaviour is annoying, because it system settings are available from the launcher in literally every other OS I've used: Android GNOME Windows Windows Phone
,
Jun 6 2016
We've discussed adding Settings to the Launcher before and decided to keep it separate. We view launching applications and managing system settings as distinct goals.
,
Jun 7 2016
Without having found the previous discussions, I should have clarified my goal.
Opening system settings has quite poor accessibility on ChromeOS. This would be an obvious step to improve it. There could be others.
---
Steps to reproduce :)
1. Alt + shift + L (three fingers)
2. Ctrl + Forward (what?)
3. Enter
4. Tab x 6
5. Enter
---
Expected behaviour:
1) It should be easy to open the settings on a new device, when you're getting to know it.
2) When providing in-person support, memorized keyboard shortcuts make it much quicker to investigate issues. Especially when it's a Settings window that has that neat type-to-search :).
Not having to memorize entirely different methods for each OS is a bonus... not essential, but breaking trail requires some justification. "Alt+1, Alt+f, s" fails that test IMO.
The standards for keyboard access are CDE, and launch key + type-to-search. I can't work out what you hope to gain v.s. the standard.
Keyboard access _should_ be a first-class citizen, including for 1) above. Particularly when the pointer device is a touchpad, at the very front of a device commonly called "laptop". Not wishing to be hyperbolic, but I suffer pain when I use the touchpad on mine ("don't do that then"). It's well-known that touchpads are a matter of personal preference.
|
||
►
Sign in to add a comment |
||
Comment 1 by abodenha@chromium.org
, Jun 6 2016Owner: tbuck...@chromium.org
Status: Assigned (was: Unconfirmed)