UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.74.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.137 Safari/537.36
Platform: 10452.74.0 (Official Build) stable-channel eve

Steps to reproduce the problem:
1. Download the attached zip file, unarchive, and load it as an unpacked extension. This is the sample code provided at https://developer.chrome.com/extensions/samples#search:input.ime unaltered.
2. Enable the IME at Settings > Languages and input > Input method > Manage input methods
3. In chrome://extensions, click on "background page" of the Test IME extension to open the inspector.
4. Switch to tablet mode and activate the Test IME.
5. Focus on the JavaScript console of the background page, and tap the space key

What is the expected behavior?
A new "onKeyEvent: context: .." log is appended to the console 

What went wrong?
No log is appended

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 66.0.3359.137  Channel: stable
OS Version: 10452.74.0
Flash Version: 

Further diagnostic info:
https://w3c.github.io/uievents/tools/key-event-viewer.html shows that the space key fires a key event with "Process" as its `key` property.

Motivation:
I'm using this IME to input Japanese on Chrome OS: https://github.com/jmuk/chrome-skk
which relies on the space key event to trigger a conversion. Right now, in tablet mode, pressing space appends a space character when it should be doing a conversion. 

The extension does receive an event when the space key is pressed by way of the onSurroundingTextChanged listener, but it's not straightforward to have to determine if the event was triggered by a space key by diffing the new surrounding text and the last known surrounding text.

I'd expect to be able to receive an onKeyEvent event, or through a separate event that represents a user request for performing conversion.
 

Deleted: basic.zip 2.9 KB

basic.zip 2.9 KB Download