`chrome.commands` API doesn't appear to accept more than 1 key's input if first key has been remapped
Reported by
sean.d.r...@gmail.com,
Apr 7 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36 Steps to reproduce the problem: 1. Remap Caps Lock to Control in `/etc/default/keyboard` and reboot 2. Try to trigger 1 Password extension with usual keystroke (`Ctrl + Shift + X`), using the remapped Caps Lock/Ctrl key This also appears in the extensions keyboard shortcut mapping screen: 1. Remap Caps Lock as above 2. Open Extensions > Keyboard shortcuts 3. Click into the 1 Password shortcut field 4. Attempt to set command to `Ctrl + Shift + X` (or anything) with the remapped Caps Lock What is the expected behavior? Chrome should accept inputs after the remapped Ctrl key, in the same way it does when the standard Ctrl key is used. What went wrong? Remapped Ctrl appears to block further input to what I am assuming is the `chrome.commands` API (based on [input form the 1 Password developers](https://discussions.agilebits.com/discussion/comment/422187#Comment_422187)). WebStore page: https://chrome.google.com/webstore/detail/1password-x-%E2%80%93-password-ma/aeblfdkhhhdcdjpifhhbdiojplfjncoa Did this work before? N/A Chrome version: 65.0.3325.146 Channel: n/a OS Version: Debian testing Flash Version:
,
Apr 8 2018
,
Apr 19 2018
Able to reproduce this issue on reported version 65.0.3325.146 using Mac, Win and Linux platform. Steps: ---------- 1. Remaped Caps Lock as above 2. Opened Extensions > Keyboard shortcuts 3. Clicked into the 1 Password shortcut field 4. Attempted to set command to `Ctrl + Shift + X` (or anything) with the remapped Caps Lock Tested this issue on M60 observing similar behavior, so considering this is a non-regression issue and marking it as untriaged. Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by sean.d.r...@gmail.com
, Apr 7 2018