(Feature request) Shortcuts need to be configurable.
Reported by
serg...@gmail.com,
Dec 18
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. Press Ctrl+Shift+Q What is the expected behavior? Chrome closing What went wrong? Nothing happens, except for an overlay suggesting an awkward combination of pressing "Alt+F", depressing Alt, waiting until the menu is shown, then pressing "X". Completely impractical. This whole reason the Ctrl+Shift+Q was removed is lack of such a basic important thing as shortcuts configuration. Ctrl+Shift+Q was hit by accident by some users and they had no way to disable it. Did this work before? N/A Chrome version: 70.0.3538.110 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 32.0 r0 Related issues: https://crbug.com/243164 (removal request) https://crbug.com/903990 (request for "Enable Ctrl+Shift+Q" flag rather than full-fledged shortcuts configuration)
,
Dec 21
As per comment#0 it seems to be a feature request hence marking it as untriaged. Tentatively adding IO>Keyboard team. Thanks.! |
||
►
Sign in to add a comment |
||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 18