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

Issue 597938 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 569997
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Google Japanese keyboard input: unable to enter enclosed alphanumerics (number within a circle) + punctuation symbols cannot be entered as full-width characters

Project Member Reported by hawkinst@google.com, Mar 25 2016

Issue description

Chrome Version       : 49.0.2623.95
OS Version: 7834.60.0
URLs (if applicable) : N/A 
Other browsers tested: N/A

Replicated issue on: HP Chromebox, Samsung Chromebox, Asus Chromebox,  HP Chromebook

Issue first noticed: 03.25.2016 (likely related to latest update to Chrome OS) 


Issue 1: unable to enter enclosed alphanumerics (number within a circle)

What steps will reproduce the problem? 
1. On a Chrome OS machine: Select Google Japanese Input (for US/JP keyboard) 
2. Select Hiragana -> https://screenshot.googleplex.com/iTzRE8u22yp.png
3. type any digit when using Google Japanese Input 
4. after pressing digit once, list displaying past selected options appears https://screenshot.googleplex.com/ex0CfJrBTnb.png
5. Hit spacebar once more for full list of options -> https://screenshot.googleplex.com/9HWrsfYprXs.png
6. hit enter to select desired option (in this case, 1 on the list above)

What is the expected result?
digit should be displayed as enclosed alphanumeric 
See expected result here on Windows 7, showing digit inside circle (using Microsoft IME and Google IME Japanese keyboards -> https://screenshot.googleplex.com/pNno4g3jGE5

What happens instead of that?
digit is simply shown as half-width digit with no circle around it



 Issue 2 : punctuation symbols cannot be entered as full-width characters 

What steps will reproduce the problem? 
1. On a Chrome OS machine: Select Google Japanese Input (for US/JP keyboard) 
2. Select Hiragana -> https://screenshot.googleplex.com/iTzRE8u22yp.png
3. type any punctuation symbol when using Google Japanese Input (E.g. " , ? ! )
4. after pressing symbol once, list displaying past selected options appears https://screenshot.googleplex.com/3M7jLsXeirv
5. Hit spacebar once more for full list of options -> https://screenshot.googleplex.com/rOdU1ndysgY
6. hit enter to select desired option (press spacebar to move between half and full-width)


What is the expected result?
symbol should change in size if full-width is selected 
See working example on Windows 7 https://screenshot.googleplex.com/ac3SdBRdWv4.png

What happens instead of that?
no change in symbol size, remains as half-width only 
https://screenshot.googleplex.com/tOANvd4ZK18




Note: Impact is 40-50 agents on Chrome OS. 
For issue 1, agents who need to use this particular symbol resort to copying web-based templates.

 Issue 2  causes slightly more inconvenience since character width in emails to customers need to be same throughout. 
Using the Tx function in gmail or Cases 1.0 will correct the issue and is a valid workaround. 

Would appreciate if this could be addressed ASAP, so as not to cause further impact on agent workflow. 




UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 7834.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.95 Safari/537.36



 
Kindly help to expedite it.

Comment 2 by hawkinst@google.com, Mar 28 2016

Note:  issue 2  -> using Tx to remove formatting, in actual fact does not correct the character width. 

Attempting to do so has no apparent effect, with punctuation remaining as half-width. 

In addition to our agents, I imagine this issue affects external users on Chrome OS too. 

Let me know if there is anything I can add that may help to get this resolved. 


Comment 3 by hawkinst@google.com, Mar 30 2016

Have noticed an additional area of concern. 

Numbers entered in full-width (Google Japanese input) on a Chrome OS device are not visibly displayed as such, showing as half-width numbers. 

To highlight this, here is a string of numbers entered on a Chromebook (HP), half width on top, full-width on bottom: https://screenshot.googleplex.com/5rMsB40pbpV (screenshot taken on Chrome OS)

In contrast, the same spreadsheet and set of numbers seen on a Windows machine clearly shows that the lower entry is entered in full-width. 
(same screen when viewed on Windows desktop: https://screenshot.googleplex.com/XxjniT9k5R8) 

This lack of visual distinction makes it more likely for an agent to enter numbers or symbols without aligning the character width, making a message to a customer appear unprofessional. 


I see there has been no movement on this ticket whatsoever. 
Would appreciate if this could be addressed ASAP. 






The Japanese IME seems to be working properly. I checked Unicode codepoint of the character at http://unicode.scarfboy.com/, and the site said it was U+2460 (CIRCLED DIGIT ONE) although I didn't see any circle on my Chromebook.

This looks to me more like a font or rendering issue. Just FYI.

The issue is more apparent if you visit this Wikipedia site with Chromebook and e.g. Windows:

https://en.wikipedia.org/wiki/Enclosed_Alphanumerics#Unicode_chart

On Chromebook, U+2460 does not have a circle.

Cc: shuchen@chromium.org js...@chromium.org
Components: Blink>Fonts
Status: Untriaged (was: Unconfirmed)

Comment 7 by e...@chromium.org, Apr 1 2016

Owner: kojii@chromium.org
Status: Assigned (was: Untriaged)

Comment 8 by kotah@chromium.org, Apr 1 2016

Cc: kotah@chromium.org
Confirmed older version is not affected and Wiki page in #c5 is properly rendered:

Chrome 48.0.2564.92 (Platform 7647.73.0)
Firmware Google_Spring.3824.129.0

Comment 9 by kojii@chromium.org, Apr 5 2016

Mergedinto: 569997
Status: Duplicate (was: Assigned)
It's probably because the harfbuzz in cros is old, dup of  issue 569997 .

Sign in to add a comment