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

Issue 606747 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[Regression]: Unwanted space is seen in omnibox suggestion when Japanese input method is selected

Project Member Reported by sc00335...@techmahindra.com, Apr 26 2016

Issue description

Version: 52.0.2715.0/8242.0.0 (Official Build) dev-channel falco,daisy,paine
OS: Chrome os

What steps will reproduce the problem?
(1)Sign in to user >> Change Input method to Google Japanese Input(for US Keyboard) 
(2)Type google in omnibox and observe the suggestion list

Expected: No space should be seen between letters of google
Actual: Unwanted spacing is seen between letters of google

This is a regression issue as it is working fine in 49.0.2623.112/7834.70.0 stable-channel Daisy.

Attaching screenshots for reference.
 
Expected.png
88.5 KB View Download
Actual.png
73.5 KB View Download
Cc: songsuk@chromium.org pucchakayala@chromium.org
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Blaze using chrome version 52.0.2715.0/8242.0.0
Owner: wuyingbing@chromium.org
Status: Assigned (was: Untriaged)
Labels: -Pri-1 Pri-2
Owner: hsumita@chromium.org
Hi,
I think it's not bug. Since in CJK characters have wide space. Usually two Latin letter have the same spaces with one CJK character.
You can select the "Wide Latin" in input tools menu.

The following is my assumption, need hsumita@chromium.org to confirm.
Even without select "Wide Latin" option, but candidates sorted by frequency.
So the wide Latin result still may appear in candidates list.


 
Status: WontFix (was: Assigned)
This is not a bug, but a (minor) conversion quality issue of Google Japanese Input.
"googled" are seven wide latin characters, and it doesn't have space (" ") characters.
It is a kind of expected behavior.

Ideally, it may be better to suggest "google" first instead of "googled".
However, I think it is a minor issue since
- Typical Japanese user turned off IME if they want to input ASCII characters like "google" or "googled".
and user don't need good suggestions in this case since
- Google Japanese Input automatically changes the composition text to "google" if user types "google".
- Typical Japanese IME (includes Google Japanese IME) converts input characters to ASCII characters by F10 key.

Sign in to add a comment