BB: Switching virtual keyboard is too slow |
||||||||
Issue descriptionDescription Switching to another IME is slow Steps to reproduce 1. Enable Google Japanese Input (not Japanese keyboard) 2. Switch keyboard from US keyboard to Google Japanese Input Actual results Switching takes 2-3 seconds and causes dismissing keyboard and popping up keyboard Reported by: yhanada (you :))
,
Jan 24 2017
Unassigned, up for grabs by new VK team :)
,
Jan 25 2017
,
Feb 8 2017
According to comments [1] in KeyboardUIContent::ReloadKeyboardIfNeeded, it's an intentional decision to hide the keyboard once the extension URL for the keyboard is changed (e.g. English <-> Google Japanese input), so to keep the UX the same as Android. The CL introduced this is [2]. Maybe we can rethink it though. [1] https://cs.chromium.org/chromium/src/ui/keyboard/content/keyboard_ui_content.cc?sq=package:chromium&dr=CSs&l=219 [2] https://codereview.chromium.org/470193002
,
Feb 9 2017
It takes about 800ms to load chrome-extension://jkghodnilhceideoidjikpgommlajknk/inputview.html (xkb extension). Ditto for Mozc (Google Japanese/Korean input). This loading time is the dominant part of the overall latency. Maybe we should cache the page and make changing IME fast for the second time.
,
Feb 16 2017
,
Feb 16 2017
,
Jun 30 2017
,
Jul 10 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by omrilio@chromium.org
, Nov 22 2016