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

Issue 689459 link

Starred by 15 users
Status: Archived
Owner: ----
Closed: Aug 21
Cc:
█ kavvaru@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

The cursor shape within chrome while typing in Korean language is a blinking vertical bar “|” instead of a blinking box.

Reported by dimitrio...@gmail.com, Feb 7 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Install Korean keyboard via windows control panel.
2. Open the chrome and switch the keyboard to Korean (alt+shift).
3. Press right "Alt" key in order to activate the Korean typing.
4. Press keys "q" "w" "e" "r"  one by one. 
5. Check the cursor's position and shape
6. Compeer with the attached print screens

What is the expected behavior?
The cursor shape while typing Korean must be blinking  block on top of the last letter.

What went wrong?
Problem description:
The cursor shape within chrome while typing in Korean language is a blinking vertical bar “|” instead of a blinking box.
In the Korean alphabet  , the letters can be concatenated  by pressing keys simultaneity or by pressing the correct letter sequence.
In  most windows application , the cursor stays on top of the last letter  in order to indicate that the specific later can be concatenated with another.
In chrome the cursor remains behind the last letter and it is just a vertical bar “|”.
This is confusing because in any other windows application like Firefox, Internet Explorer, MS Outllok etc  the cursor shape is a square block.
In chrome the concatenation works correctly
The problem is the cursor shape itself and the fact that is stays behind the last letter  .

Are others seeing the same problem?
Many users from Korea complain for this problem. Please check for example the below conversations.

Https://www.reddit.com/r/Korean/comments/1mz288/helptext_input_cursor_in_front_of_a_syllable/

Https://productforums.google.com/forum/#!Topic/chrome/RC2JHB2DPNQ

What's the correct behavior?
The cursor shape while typing Korean must be blinking  block on top of the last letter .   
Is the behavior different in other browsers?
Yes the behavior is different with the other browsers. IE,FF and safari are using block character as cursor.
Please check the attached prints screens below

Is it a regression?
No, it is manual tests

Details of the environment:
Windows 7 and also Window 10
Chrome Version 56.0.2924.87 (64-bit)
We test it with Chrome 53 , 55 and 56 the functionality is the same 

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0
Chrome_the_problem.png
195 KB View Download
Firefox.png
79.3 KB View Download
Internet_Explorer.png
57.3 KB View Download
Safari.png
298 KB View Download
WINDOWS_IN_GENERAL.png
65.3 KB View Download
MS_outlook.png
53.7 KB View Download
NODEPAD++.png
28.8 KB View Download
VirtualBox.png
94.8 KB View Download

Comment 1 by ligim...@chromium.org, Feb 8 2017

Labels: Needs-Triage-M56

Comment 2 by ligim...@chromium.org, Feb 8 2017

Labels: Pri-1
****Bulk Edit****

Setting as P1 for test team to prioritize in triaging.

Comment 3 Deleted

Comment 4 by darrin.j...@gmail.com, Feb 15 2017 

In the mobile version of Chrome the cursor is to the right instead on the left on Windows. Should be an inverse block cursor over the current character position.

Comment 5 by kavvaru@chromium.org, Feb 20 2017

Cc: kavvaru@chromium.org
Components: -UI UI>Input>Text>IME
Labels: -Needs-Triage-M56 M-58 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7,Mac 10.12.3 using chrome version 56.0.2924.87 and canary 58.0.3016.0.

This is non regression issue as the issue seen from M30 old builds.
Marking it as Untriaged to get more inputs from dev team.

Thanks,

Comment 6 by robliao@chromium.org, Aug 21

Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Comment 7 by robliao@chromium.org, Aug 21 

Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
►

Sign in to add a comment