chrome.input.ime - Property 'input' does not exist |
|||
Issue descriptionChrome Version: 71.0.3578.98 (Official Build) (64-bit) OS: MacOS Create an Extension with the 'input' permission defined, either with or without an input_component key defined in the manifest. In a background script, assign `chrome.input.ime` to a variable. What is the expected result? On all OSes, chrome.input.ime should exist, at the least if the permission is defined. What happens instead? On Linux, WIA. ChromeOS - WIA. MacOS - `Uncaught TypeError: Cannot read property 'ime' of undefined` Windows - Not tested yet Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. Example: https://chrome.google.com/webstore/detail/canner-for-sst/chiaccalogdnegninlpepablimmcfplb ( version 2018-12-17 17:58:51 cl/225279484 // 0.65.18351.958 )
,
Dec 18
(Not my area of expertise, but the docs for this say that it's for CrOS, so this is maybe WAI)
,
Dec 18
The documentation does state ChromeOS, however this does work I intend on Linux and on ChromeOS while developing the extension. I used google.com/inputtools/chrome as an example of it working (at least in the limited way I'm looking for) on other OSes, plus the experience on Linux during development. I'm specifically looking for listening to and injecting keystrokes in non-tab contexts, mainly Chrome apps. In testing, this works on Linux except for password fields, which is exactly what I wanted.
,
Dec 21
The documentation says that the API is for ChromeOS, however the bindings are exposed to chromeos, win, linux. This doesn't seem right. Assigning to shuchen@ who owns the API.
,
Dec 21
Link in code which shows the bindings are available to chromeos, win, linux- https://cs.chromium.org/chromium/src/chrome/common/extensions/api/_permission_features.json?type=cs&q=input+file:features.json&g=0&l=409.
,
Dec 24
It is by design to support the IME extension APIs on CrOS/Win/Linux and NOT Mac. The online help doc needs to be fixed to reflect that. However, the APIs are fully supported on Chrome OS, but only a subset of APIs are supported on Windows/Linux. In the API JSON file, they have been specified by the "platforms" properties. Is there a way to reflect the "platforms" spec to the online help doc?
,
Jan 16
(6 days ago)
|
|||
►
Sign in to add a comment |
|||
Comment 1 by lgrey@chromium.org
, Dec 18