Issue metadata
Sign in to add a comment
|
1Password command is captured and sent to Sources when DevTools window is not active
Reported by
jsw.jame...@gmail.com,
Nov 30 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: This issue follows https://bugs.chromium.org/p/chromium/issues/detail?id=778735 which was mistakenly reported under DevTools because I don't know where the code for capturing key events resides. Issue is intermittent, but many people have reported and repro'd 1. DevTools can be open as separate window, not even on Sources panel. This will prove that the command is captured by Chrome UI and routed to DevTools. 2. From CMD+\ and notice that 1Password dialogue will no longer open, focus shifts to DevTools, panel changes to Sources, and Debugger starts 3. Even with DevTools closed, the event is captured and 1Password is not receiving the keystroke. I have to press CMD+Opt+\ and use the other dialogue What is the expected behavior? CMD+\ should not be captured by Chrome UI, and should be accessible to Chrome Extensions What went wrong? Instead of having a shortcut to login, I'm randomly switched to the background window and Sources panel Did this work before? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.13.0 Flash Version:
,
Nov 30 2017
[Mac triage] I don't have 1password installed, but happened to run into this: https://discussions.agilebits.com/discussion/79239/keyboard-shortcut-in-chrome-not-working Does restarting 1password work as in that link? From what I can tell, the shortcut is registered by their native app and not the extension, so I'm not really sure what we can do.
,
Nov 30 2017
The reason I say it's not 1Password is that DevTools is activated, switches panels, and starts the debugger, which indicates that Chrome is capturing the keypress events.
,
Nov 30 2017
The only plausible explanation would be that 1Password is ignoring the keypress and instead re-emitting the event to the DevTools Sources panel, but that seems unlikely.
,
Dec 3
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 7
Mac triage: WontFix - from the context in 778735 and specifically comment 11 on that bug, it sounds like Chrome is behaving properly here. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Nov 30 2017