CJK candidate windows doesn't show up after exiting tablet mode |
||||||||||
Issue descriptionChrome Version : 61.0.3162.0 Platform : 9765.0.0 - Caroline What steps will reproduce the problem? (1) Set IME to Chinese Pinyin and (2) enter "tian" on input field, and select “天” from the Chinese candidate window (3) flip the device into tablet mode (4) touch on any input field to bring up Virtual keyboard (5) touch "ti", and select any Chinese character (6) exit tablet mode (7) enter "tian" on input field again, and check the Chinese candidate window What is the expected result? The candidate window should appear. What happens instead? It doesn't show up. Please provide any additional information below. Attach a screenshot if possible. Able to see the candidate window after re-signing the user. Reproduce the issue on Chrome 59.0.3071.134/CrOS 9460.73.0- Cyan
,
Jul 25 2017
The root cause is: when flip to tablet mode, then flip back tablet mode. Javascript running in inputview container doesn't send the state change to background. May inputview container is killed by OS at once. It doesn't have enough time to info background.
,
Jul 25 2017
The root cause is: chrome.runtime.sendMessage in background can't be trigger onMessage any more. Will fix tomorrow.
,
Jul 25 2017
,
Jul 31 2017
,
Aug 4 2017
Able to see the issue after exiting virtual keyboard. Chrome 61.0.3163.33/ CrOS 9765.15.0 - Quawks. Steps : (1) Set IME to Chinese Pinyin (2) open chrome://md-settings/languages >>Input method (3) enable the 'Show input options in the shelf' option (4) click on Emoji palette in Input icon in the shelf to bring up the VK (5) exit the VK (6) enter "tian" on omnibox and check the candidate window Then, the candidate window doesn't show up.
,
Aug 15 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/e9416ce3955d4106a98322b1d518f2e8413dadac commit e9416ce3955d4106a98322b1d518f2e8413dadac Author: Yingbing Wu <wuyingbing@google.com> Date: Tue Aug 15 05:19:40 2017
,
Aug 15 2017
,
Aug 15 2017
This bug requires manual review: M61 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 15 2017
Approving merge to M61 Chrome OS.
,
Aug 17 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/c91bf203d6d3b55003298a37b55bf59c1a939286 commit c91bf203d6d3b55003298a37b55bf59c1a939286 Author: Yingbing Wu <wuyingbing@google.com> Date: Thu Aug 17 00:49:51 2017
,
Aug 21 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 23 2017
,
Aug 24 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 24 2017
Verified in chrome 61.0.3163.61/CrOS 9765.38.0 - kevin, 62.0.3193.0/9869.0.0 - Caroline |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by shuchen@chromium.org
, Jul 25 2017Owner: wuyingbing@chromium.org
Status: Assigned (was: Untriaged)