Issue metadata
Sign in to add a comment
|
The first character when searching in the OmniBox is not passed to the input method
Reported by
qiu...@gmail.com,
Jan 12
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 0. Assume we have assigned keyword "k" to a certain search engine. 1. Type "k" and space in the OmniBox. This causes Chrome to enter into the mode that accepts a search text. 2. Switch to a non-English input method, which, in my case, Chinese. 3. Type whatever keys, and the first character is treated as English and not passed to the input method in use. 3. What is the expected behavior? When it s active, whatever typed in the OmniBox should be fed to the input method. What went wrong? It looks like Chrome hijacked the first character. Did this work before? Yes I can't tell - maybe 65-ish Chrome version: 71.0.3578.98 Channel: stable OS Version: OS X 10.14.2 Flash Version:
,
Jan 12
,
Jan 14
,
Jan 14
As per comment #3, as this is a duplicate issue, removing Needs-Bisect label. Thanks.. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Jan 12