Chrome OS IMEs' configuratio pages shows a weird extension name: __MSG_chos_inputtool_title__ |
||||||||||
Issue descriptionChrome OS Version: M57-9200.0.0 and M58-9212.0.0 Steps To Reproduce: (1) Sign in (2) Open settings (3) Press Keyboard settings > Change language and input settings > Add > Chinese (simplified) (4) Check Pinyin input method (5) Click "Configure..." Actual Result: A new Chrome tab opens to show the configuration page at "chrome-extension://<the-ime-extension>/hmm_options.html?code=...", but Omnibox shows a raw, not-really-human-readable extension name (__MSG_chos_inputtool_title__). See the screen shot. That part should be something like "Google Input Tool for Chrome OS." How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? The product looks unpolished. * M56 didn't have the issue. * Other IMEs (like Google Japanese Input) have the same issue.
,
Jan 25 2017
I've checked and confirmed that the extension's _locales/en/messages.json contains: "chos_inputtool_title": {"message": "Google Input Tools"}.
The cause seems that Chromium doesn't support localized extension name.
Who should own this issue?
,
Jan 25 2017
,
Jan 25 2017
,
Jan 26 2017
It only reproduces on M57+.
,
Jan 27 2017
,
Jan 27 2017
FYI, Task Manager (Search+Esc) seems to have the same issue.
,
Jan 28 2017
Jungshik, mind taking a look? Thanks.
,
Feb 8 2017
I can't get to this issue soon. In the meantime, I wonder if songsuk@ can bisect it (I'm not sure if it's feasible to bisect for Chrome OS) to narrow down the range.
,
Feb 8 2017
I don't think this is a regression. The design of Omnibox was changed in M57 so that it would show an extension name for chrome-extension://... URLs, and that made the weird string visible to the user. The actual problem here I believe is that a user-friendly name has _never_ been given to the string (__MSG_chos_inputtool_title__).
,
Feb 8 2017
Seems, on M57, a extension name appears on the omnibox. Could you check the "name:" field on manifest.json.
,
Feb 17 2017
Good build : Chrome 57.0.2958.0 / CrOS 9111.0.0 - glimmer Bad build : Chrome 57.0.2959.0 / CrOS 9113.0.0 - glimmer Seems, the following change provided new ui on omnibox. https://chromium.googlesource.com/chromium/src/+/172e00cdced29d37051bd7fc8faaeedb7416653c Since I'm not able to check resource files, could you check "name": on manifest.json. "__MSG_chos_inputtool_title__" need to be changed to a user-friendly name.
,
Jun 26 2017
This is still an issue. Who would be the right person to choose a name for the ChromeOS input tool extension?
,
Jun 27 2017
The issue is fixed (comment#16) on Chrome60.0.3112.41/CrOS 9592.29.0 (Link), Chrome 60.0.3112.45/CrOS 9592.36.0(Sakte).
,
Jun 27 2017
Verified the issue on Chrome 61.0.3130.0/CrOS 9671.0.0 - Candy |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by yusukes@chromium.org
, Jan 24 2017