onscreen keyboard does not open when running on linux desktop |
|||
Issue description
1) Build & Run chrome for chromeos on linux desktop
2) Enable on-screen keyboard from accessibility settings
3) Click "keyboard" tray button
I get the following message:
[4170:4170:0616/110943:ERROR:CONSOLE(0)] "(BLESSED_EXTENSION context for mppnpdlheglhdfmldimlhpnegondlapf) extensions::schemaUtils:34: Uncaught Error: Invalid value for argument 1. Property 'hotrodmode': Unexpected property.{Error: Invalid value for argument 1. Property 'hotrodmode': Unexpected property.
at validate (extensions::schemaUtils:34:13)
at handleResponse (extensions::sendRequest:72:9)}", source: chrome-extension://mppnpdlheglhdfmldimlhpnegondlapf/index.html (0)
This used to work, and according to bshe@ this should still work.
wuyingbing@, shuchen@ do you have any clue?
,
Jun 17 2016
Looks like an issue in the preloaded VK extension 'mppnpdlheglhdfmldimlhpnegondlapf'. Biao, any ideas?
,
Jun 17 2016
I did some research today and found the root cause. Looks like we didn't define hotrodmode field for getKeyboardConfig. And debug version enforces the check so the keyboard failed to load. It is a easy fix. I can take care of it.
,
Jun 20 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/465d55d04e5751c27aef61408183a26ad7d3cf24 commit 465d55d04e5751c27aef61408183a26ad7d3cf24 Author: bshe <bshe@chromium.org> Date: Mon Jun 20 01:34:46 2016 Fix js error in VK on debug build The js error is because we forgot to add hotrodmode field in API's json file. This CL should fix it. BUG= 620936 Review-Url: https://codereview.chromium.org/2072333002 Cr-Commit-Position: refs/heads/master@{#400622} [modify] https://crrev.com/465d55d04e5751c27aef61408183a26ad7d3cf24/extensions/common/api/virtual_keyboard_private.json
,
Jun 20 2016
,
Jun 20 2016
thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by osh...@chromium.org
, Jun 17 2016