Status menu shortcut does not work when brightness/volume popup visible
Reported by
anowlcal...@gmail.com,
Aug 18 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS armv7l 9460.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.91 Safari/537.36 Platform: 9460.60.0 (Official Build) stable-channel nyan_big Steps to reproduce the problem: 1. Press one of the brightness/volume adjustment keys to show the brightness or volume slider in the bottom-right 2. Press alt-shift-S to open the status menu 3. The status menu doesn't open What is the expected behavior? Pressing alt-shift-S should always open the status menu, dismissing any brightness/volume level adjustment slider in the way. What went wrong? When the brightness/volume slider is visible in the bottom-right corner, the status menu cannot be opened with the keyboard shortcut (alt-shift-S), but it can still be opened by clicking the profile picture. Did this work before? No Chrome version: 59.0.3071.91 Channel: stable OS Version: 9460.60.0 Flash Version: 26.0.0.137
,
Nov 20 2017
Alt+Shift+S does close the volume/brightness slider immediately, but agreed that it should instead open the system menu.
,
Nov 21 2017
Huh, that's changed since I opened the bug then :) There's some really weird inconsistencies in this bit of the UI in general. For example, try pressing alt-shift-S, then alt-shift-N -- the message centre opens in front of the system menu, which is kind of odd (this also works the other way around). Then press Esc, and the system menu closes, but not the message centre (in fact the message centre will not close in response to an Esc press at all). However, if you open either of the system menu or message centre by mouse rather than keyboard shortcut, they will not open in front of each other. Also, whilst alt-shift-S closes the volume/brightness sliders, alt-shift-N doesn't -- press Mute, then press alt-shift-N twice quickly, and the volume slider will still be visible.
,
Nov 21
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 13
Bulk-assigning unassigned status area bugs to me.
,
Dec 13
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by r...@chromium.org
, Aug 18 2017Status: Untriaged (was: Unconfirmed)