New issue
Advanced search Search tips

Issue 714668 link

Starred by 6 users

Issue metadata

Status: Duplicate
Merged: issue 383093
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Duplicate normal character + Vietnamese character for Vietnamese input

Reported by daohie...@gmail.com, Apr 24 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Use any Vietnamese keyboard input software (example: Unikey, Gõ Tiếng Việt, VietKey) with Unicode charset and any input method
2. Input word with Vietnamese character at the beginning of the word (example: ă, â, đ, ê, ư, ô, ơ) to the search bar
3. Have an excess non-replaced character + Vietnamese character: ê --> eê

What is the expected behavior?
Display only Vietnamese character: "được"  not "dđược", "ước" not "uước", "ông" not "oông"

What went wrong?
Words displayed incorrectly (only for updated Chrome browser with 
old Chrome history)

Did this work before? N/A 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 10.0
Flash Version: 

 If you clean the history, the problem will stop, but as soon as the history re-syncs with Chrome History on the cloud, you'll have the problem again. Besides, most of the users don't want to erase the history
 
Labels: Needs-Milestone

Comment 2 by ajha@chromium.org, May 18 2017

Components: -UI UI>Internationalization UI>Input>Text>IME
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
Tested this issue on Windows 10 with Chrome #58.0.3029.110 

Changed keyboard to Vietnam layout and chrome language to Vietnamese

Observed that it is displaying  Vietnamese words are displaying correctly.

Attaching a screen-cast for reference.

daohieu61@ Could you please look into it and let us any steps i have missed while reproducing the issue.

If possible could you please help us with the screen-cast of this issue.

Thank You...


Issue 714668-1.mp4
1.1 MB View Download
Cleaning history makes me think this is a problem with an extension or your synced history / synced extensions.  Can you try disabling all extensions and seeing if the problem reproduces?  
Every computer that uses Unikey got this problem (I've tested on more than 10 PCs ). And nobody in Vietnam uses Windows keyboard because that's extremely inconvenient. This is the link for unikey http://www.unikey.org/bdownload.php Sorry, no video. But here's the screenshot
Capture.JPG
100 KB View Download
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 2 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-TestConfirmation
Can someone with a Windows device please install Unikey to test/confirm this bug?  And clarify the situations under which it occurs?  Adding the appropriate flag. 
 thanks!
(Clarification: for example: does it happen in web pages?  In the omnibox?  In the find-in-page box?)
It doesn't happen in web pages nor in the finding box, only in the omnibox.

Comment 10 by ajha@chromium.org, Sep 7 2017

Cc: ajha@chromium.org
Components: UI>Browser>Omnibox
Labels: -Needs-TestConfirmation M-63
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue using Unikey on Windows-10, latest canary(63.0.3207.0) but this is showing inconsistent behavior on chrome version: 61.0.3163.79. At first on fresh installation this showed the buggy behavior but once I kept the system idle and reopened it after 2 hrs, this started working fine. The buggy behavior is observed only in omnibox but works fine elsewhere.

Attached is the screen-cast of the buggy behavior on canary and correct behavior on 61.0.3163.79.

Marking this as Untriaged for more inputs and further investigation of this.
714668.mp4
4.4 MB View Download
I've figured out what caused the problem, it's the browsed page suggestion. When I made a new profile, the omnibox worked perfectly without duplication. The problem only occurred when the history had data which it could make suggestion from.
How to reproduce that: 
1. Create a new profile
2. Use unikey in the omnibox (e.g. typing character "e" twice) --> watch it produces an "ê" normally
3. Go to a page (example.com)
4. Type "e" twice again --> it produces eê which isn't a legal character or word

Mergedinto: 383093
Status: Duplicate (was: Untriaged)

Sign in to add a comment