Entering some Unicode characters causes Chrome to trap the keystrokes |
||||||
Issue descriptionChrome Version: 56.0.2924.87 (Official Build) (64-bit) OS: Windows 10 What steps will reproduce the problem? (1) Visit any page with a <textarea> or other text entry element (2) Enter Unicode characters with the Alt+NumPad method, e.g. Alt+0237 (i with acute accent) (3) In the case of i with acute (at least), Chrome navigates to the home page (e.g. moma for Googlers). Other characters, e.g. Alt+0235 (ë), do not cause this problem. What is the expected result? I want to see the i with acute accent show up in the text area. :) What happens instead? i with acute accent appears, but then the page immediately navigates to the home page.
,
Mar 15 2017
+ core/editing OWNERS :)
,
Mar 15 2017
,
Mar 15 2017
I found another one: When you try to type it into a textarea, em-dash (Alt+2014) causes Chrome to navigate back to the previous page. When you type Alt+2014 into the Omnibox, however, you get a black rectangle character, instead of an em-dash, and without causing any weird navigation.
,
Mar 15 2017
It seems dead Alt+{Digit}* handling incomplete in browser side.
Alt+0237 = U+00ED
Alt+2014 = U+07ED
Related Windows Virtual Key (VKEY) handling?
,
Mar 16 2017
Not a blink issue but a UI navigation issue.
,
Mar 16 2017
This isn't so much navigation as keyboard shortcuts, I think. (I'm certainly not familiar with how keyboard shortcuts lead to navigations.) |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tkent@chromium.org
, Mar 14 2017