New issue
Advanced search Search tips

Issue 679461 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Ctrl + Shift + E Combination not working in Chrome

Reported by mtgcs2...@gmail.com, Jan 9 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Hold Ctrl
2. Hold Shift
3. Press E

What is the expected behavior?
Chrome fires a keypress event for E key

What went wrong?
No keypress event is fired. Only a keyup event is fired when I release the E key. 

Did this work before? Yes Unsure. It broke in the last month or two. 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: Linux u705a0fcae861583c82b1 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Flash Version: Shockwave Flash 24.0 r0

This key combination works fine in Firefox on the same machine so it's not the OS or any other programs eating the input. This also happens in incognito mode with no extensions running. 

I've attached a screenshot showing the w3c key-event-viewer (https://w3c.github.io/uievents/tools/key-event-viewer.html) in both Chrome and Firefox on the same machine. To get this screenshot I pressed and held Control, then pressed and held Shift, then pressed E, then released all 3.
 
keyboard-events.png
131 KB View Download
Also Ctrl + E and Shift + E both work fine and emit all events. As far as I can tell all other Ctrl + Shift + <KEY> combinations work too. 

Comment 2 by woxxom@gmail.com, Jan 10 2017

Do you have Tampermonkey extension? It adds a browser-scope Ctrl-Shift-E to enable/disable the extension, which is also active in incognito mode. The shortcut keys may be disabled or customized on chrome://extensions page in browser settings.

Comment 3 by ajha@chromium.org, Jan 10 2017

Components: -UI UI>Input>KeyboardShortcuts
Labels: Needs-Triage-M55 Needs-Bisect
Labels: Needs-Feedback
Unable to reproduce the issue on Ubuntu 14.04 using stable 55.0.2883.87 and latest dev 56.0.2924.51.
Could you please review the attached screen cast and let us know if any.
679461_jan_10.ogv
1.4 MB View Download

Comment 5 Deleted

Comment 6 by mtgcs2...@gmail.com, Jan 10 2017

It was Tampermonkey! Thanks for pointing that out. I don't understand how Tampermonkey can block the key combination in Incognito mode when "Allow in Incognito" is not ticked.

I guess that's the real bug here, if a extension is not enabled in Incognito it should not be able to manipulate key bindings in Incognito mode. That seems like a security flaw to me. 
Components: Platform>Extensions
Labels: -Needs-Feedback -Needs-Bisect -Needs-Triage-M55 hasbisect-per-revision M-57 OS-Windows
Owner: shuchen@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for the update.
Used the below extension and was able to reproduce it on Win 10 and Ubuntu 14.04 using stable 55.0.2883.87 and canary 57.0.2979.0.

Bisect info:
=============
Good: 50.0.2657.0
Bad : 50.0.2658.0

You are probably looking for a change made after 376931 (known good), but no later than 376941 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/0e3154168e264418c886699162394e87af067964..afb306c03fa249d482f3116816aa5a6c5c1d5fe3

Suspect:
Review URL: https://codereview.chromium.org/1703683003
shuchen@: Could you please take a look into this if its related to your change.

Note: Its working fine on Mac 10.12.2.
Status: WontFix (was: Assigned)
This is by design because the extension sets the shortcut command key: Ctrl+Shift+E, which will cause the related key events consumed.

Please refer to the screenshot.
Screen Shot 2017-01-13 at 2.31.53 PM.png
63.8 KB View Download
Just read #6, mtgcs2000@, can you please open a separated bug to track the real issue? Thanks!

I cannot access the  issue 681112 . What's wrong?

It says: "You do not have permission to view the requested page.
Reason: User is not allowed to view this issue"
It looks like because I opened it as a security issue it's only visible to the security team. I think they'll make it publicly visible soon as it's already visible here. 

Sign in to add a comment