New issue
Advanced search Search tips

Issue 870751 link

Starred by 3 users
Status: Fixed
Owner: ----
Closed: Sep 10
Cc:
shuchen@chromium.org
wuyingbing@chromium.org
hungte@chromium.org
yhanada@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

IME extension wrongly sends out keys during composition

Project Member Reported by victorhsieh@chromium.org, Aug 3 
Chrome Version: latest dev channel (69.0.3497.21 I believe)
OS: Chrome OS 10895.10.0 (tried on caroline)

What steps will reproduce the problem?
(1) Install jscin: https://chrome.google.com/webstore/detail/jscin-javascript-based-ch/cdkhibgadomdghgnknpmgegpjjmfecfk
(2) Switch to this IME
(3) Type something

What is the expected result?

Composition window pops up.  Key is NOT sent to the page.

What happens instead?

Composition window pops up.  Key IS sent to the page.

Comment 1 by yusukes@chromium.org, Aug 3

Cc: shuchen@chromium.org yhanada@chromium.org
+IME folks

Comment 2 by hungte@chromium.org, Aug 6 

FYI jscin source is here https://github.com/google/jscin

It's following the IME API and do commitText as here: https://github.com/google/jscin/blob/master/src/chrome/croscin.js

Are there anything changed in IME API?

Comment 3 by shend@chromium.org, Aug 8

Cc: wuyingbing@chromium.org
Hi Yingbing, do you know if there were any changes to the IME API?

Comment 4 by shuchen@chromium.org, Aug 14 

There shouldn't be related recent changes in IME API.

And it is weird that I failed to make jscin IME work on my device.
Its background js fails to receive the chrome.input.ime.onFocus event.

Comment 5 by hungte@chromium.org, Aug 14 

I see a deprecated warning at background page when running on Chrome@Linux.

Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

Have we recently merged the change so Chrome on Chrome OS is also not accepting synchronous call?

Comment 6 by hungte@chromium.org, Aug 14 

well probably not related... I see same warning on browser 67.* and it still works.

Comment 7 by wuyingbing@chromium.org, Sep 10 

It should be bug. WYDT, shuchen@?

Comment 8 by victorhsieh@chromium.org, Sep 10

Status: Fixed (was: Untriaged)
The problem seems to be fixed on latest Dev.
►

Sign in to add a comment