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

Issue 664334 link

Starred by 2 users
Status: Verified
Owner:
azurewei@chromium.org
Closed: Nov 2016
Cc:
█ gkihumba@chromium.org
shuchen@chromium.org
█ xiangye@chromium.org
pucchakayala@chromium.org
█ tdander...@chromium.org
dhadd...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

List number/Enlish is unreadable in CJK candidate windows

Project Member Reported by songsuk@chromium.org, Nov 10 2016 
Chrome Version       : 56.0.2915.0
Platform             : 8978.0.0 (Official Build) dev-channel peppy

What steps will reproduce the problem?
(1)  set IME to Simplified Chinese Pinyin input method
(2)  enter 'ti' in any input fields and check the candidate window


What is the expected result? What happens instead?
The list numbers appear garble (cjk.png)

Please provide any additional information below. Attach a screenshot if
possible.
Not reproduce the issue on Chrome 56.0.2905.0/CrOS 8953.0.0 -Candy
cjk.png
317 KB View Download

Comment 1 by songsuk@chromium.org, Nov 11 2016

Summary: List number/Enlish is unreadble in CJK candidate windows (was: List number is garble in CJK candidate windows)
English/numbers are hardly readable on the candidate window.
ja (1).png
321 KB View Download
zh (1).png
317 KB View Download

Comment 2 by songsuk@chromium.org, Nov 11 2016

Labels: OS-Chrome

Comment 3 by shuchen@chromium.org, Nov 11 2016

Owner: tdander...@chromium.org
Status: Assigned (was: Untriaged)
Summary: List number/Enlish is unreadable in CJK candidate windows (was: List number/Enlish is unreadble in CJK candidate windows)
Hi Terry, this seems related to MD changes. Can you please take a look? Thanks.

Comment 4 by tdander...@chromium.org, Nov 11 2016

Cc: tdander...@chromium.org xiangye@chromium.org
Owner: azurewei@chromium.org
I don't think this is related to the MD work since we shouldn't have touched that surface. But let me assign to the IME team to see what they think.

Comment 5 by azurewei@chromium.org, Nov 20 2016

Status: Fixed (was: Assigned)
This bug seems already been fixed in Chrome 57.0.2926.0. Please verify it.
Project Member

Comment 6 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Nov 20 2016

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-56; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-56 label, otherwise remove Merge-TBD label. Thanks.

Comment 7 by songsuk@chromium.org, Nov 22 2016

Status: Verified (was: Fixed)
Verified. chrome 56.0.2924.3/CrOS 9000.3.0 - Pi, Clapper
Project Member

Comment 8 by sheriffbot@chromium.org, Dec 16 2016

Labels: Merge-Review-56 Hotlist-Merge-Review
This bug requires manual review: No test file found in commits.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 16 2016 

This bug requires manual review: No test file found in commits.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by dimu@google.com, Dec 16 2016

Labels: -Merge-Review-56 -Hotlist-Merge-Review
[Automated comment] removing mislabelled Merge-Review-56, Hotlist-Merge-Review
Project Member

Comment 11 by sheriffbot@chromium.org, Jan 30 2017

Labels: -Merge-TBD
►

Sign in to add a comment