New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 812310 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 780146
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Most keyboard shortcuts don't work when all windows are minimized

Project Member Reported by michae...@chromium.org, Feb 14 2018

Issue description

Chrome Version: 65.0.3322.0

Most keyboard shortcuts are disabled when only the wallpaper is in the foreground (ie, when no windows are open and un-minimized). This includes the Launcher key; shell shortcuts like Alt+Shift+S (system tray), Ctrl+Alt+? (keyboard shortcut overlay), or Ctrl+Alt+. (multi-profile switcher); and launching shelf items like Alt+1.

The only shortcuts that seem to work are Alt+Tab and the Assistant key. Hotkeys like volume, brightness, and the window switcher also work.

If a window or some system UI is open, shortcuts work again.

Happens for both accounts in multi-profile mode.

1. Close or minimize all windows.
2. Press the Launcher key or a keyboard shortcut like Alt+Shift+S, Alt+1, Ctrl+Alt+?.

Nothing happens.

3. Show shell UI such as right-clicking the desktop, opening the system tray, or opening the notifications tray.
4. Press a keyboard shortcut.

Shortcuts work.
 
Components: -UI>Shell
Cc: warx@chromium.org minch@chromium.org weidongg@chromium.org yhanada@chromium.org
I'm not sure which one of you fixed this bug recently (or is it a different bug?)

Please dupe into the appropriate bug if applicable.

Comment 3 by minch@chromium.org, Feb 16 2018

Not sure whether it is the same one(looks similar). I fixed one shortcut issue recently and merged back to 65.0.3325.0
https://bugs.chromium.org/p/chromium/issues/detail?id=780146
Mergedinto: 780146
Status: Duplicate (was: Untriaged)
This did occur the same day I had played around with tablet mode, and I haven't noticed this after updating to 3325 -- sounds like the same issue, then. Thanks!

Sign in to add a comment