New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 694930 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Keyword search box of dmenu: after inputting voiced consonant or p-sound in the kana syllabary, character input becomes not available.

Reported by smcs...@gmail.com, Feb 22 2017

Issue description

Steps to reproduce the problem:

[steps]
[In case of input with keypad]
1. Open Chrome
2. Go to smt.docomo.ne.jp
3. Tap on search bar (Japanese keyboard appears.)
4. Input one byte katakana character of voice consonant or p-sound in kana syllabary in the search bar in the page then fix it.(Tap on 「か」then「小゛゜」. Then scroll to find 「ガ」(the narrow character and not the wide one) and select it. )(This is one byte character)
5. Tap on 「あ」「か」「さ」「た」「な」「は」「ま」「や」「ら」「わ」.
6. Notice that those tapped characters are not correctly shown in the search bar. (This is the claimed issue.)

[In case of input with QWERTY]
1. Launch Chrome application and access to the top page of dmenu. (Also you can access to the top page of such as Google or Yahoo.)
2. Input one byte katakana character of voice consonant or p-sound in kana syllabary in the search bar in the page then fix it.
3. Input consonant of character (A).
4. Input vowel of character (B).

 -> At step4, character is not input.

What is the expected behavior?
On using Chrome application, character should be able to be input after voiced consonant or p-sound in the kana syllabary is input.

What went wrong?
User is not able to input the character after selecting voiced consonant or p-sound in the kana syllabary in input.

Did this work before? N/A 

Chrome version: <Copy from: 'about:version'>  Channel: n/a
OS Version: 6.0, 7.1
Flash Version: 

Issue is reproduced in Nexus 5X android version: 7.1 with Chrome app: 56.0.2924.87
Issue is reproduced in Nexus 5X android version: 6.0 with Chrome app: 55.0.2883.91

With Chrome 54.0.2840.85, the issue is not reproducible.

 
Cc: ram...@chromium.org
Labels: triage-te

Comment 2 by ram...@chromium.org, Feb 22 2017

Labels: Needs-Feedback
Can you provide a screen capture or video shot?
Cc: rbasuvula@chromium.org
Labels: Triaged-Mobile
Status: WontFix (was: Unconfirmed)
Marking it as Won't Fix since there are no feedback from user more than a month.Feel free to raise a new issue if still facing.

Thank You!

Sign in to add a comment