New issue
Advanced search Search tips

Issue 903710 link

Starred by 1 user
Status: Duplicate
Merged: issue 896962
Owner: ----
Closed: Nov 12
Cc:
viswa.karala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

First letter doesn't included by IME (Chinese/Japanese) when using search engine in address bar

Reported by human.p...@gmail.com, Nov 9 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.44 Safari/537.36

Steps to reproduce the problem:
1. Entering search mode by using any keyword+tab. I test with google.com or en.wikipedia.org + tab
2. Switch on IME. I tested:

1) Sogou Pinyin Input
2) Microsoft PinYin New Experience 
3) Microsoft Japanese input
4) Baidu Japanese input

3. Try to type in any words

What is the expected behavior?
The latin characters should be used by the IME to convert to words in Japanese/Chinese

What went wrong?
The very first Latin letter will be straight on screen, not triggering IME properly

Did this work before? Yes It works fine just yesterday, not sure about the version unfortunately. 

Chrome version: 71.0.3578.44  Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

It is broken on Canary (Version 72.0.3606.0 (Official Build) canary (64-bit)) too.
Desktop 2018.11.09 - 03.43.00.02.mp4
13.0 MB View Download

Comment 1 by human.p...@gmail.com, Nov 9 

 doesn't included-> doesn't get included

Comment 2 by human.p...@gmail.com, Nov 9 

The behavior is slightly different on my Win10 laptop (but still bugged).

The very first letter will still be directly on screen, but ALSO gets included by IME:
Win10-chromebeta.png
42.6 KB View Download

Comment 3 by phanindra.mandapaka@chromium.org, Nov 11

Labels: Needs-Bisect Needs-Triage-M71

Comment 4 by innatere...@gmail.com, Nov 12 

Duplicate of issue 896962. (sigh)

Comment 5 by viswa.karala@chromium.org, Nov 12

Cc: viswa.karala@chromium.org
Labels: -Needs-Bisect Triaged-ET
Mergedinto: 896962
Status: Duplicate (was: Unconfirmed)
Thanks for filing the issue!

This issue seems to be similar to Issue: 896962, hence merging into it and marking it as Duplicate.
Note: Feel free to Un-Dupe it if not the case.

Thanks!
►

Sign in to add a comment