New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 660137 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ yabinh@chromium.org
chaopeng@chromium.org
█ aelias@chromium.org
dtapu...@chromium.org
yosin@chromium.org
█ chongz@chromium.org
█ rlanday@chromium.org
changwan@chromium.org
editing-dev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 652397



Sign in to add a comment

No 'compositionstart' event when starting composition from existing text

Project Member Reported by chongz@chromium.org, Oct 27 2016 
Version: Chrome Canary 56.0.2901.3
OS: Android 6.0.0; Nexus 7

What steps will reproduce the problem?
(1) Go to https://cdn.rawgit.com/w3c/uievents/gh-pages/tools/key-event-viewer.html
(2) Using Google Keyboard English (US), focus input field and press key 'A'
(3) Tap blank area to remove focus
(4) Focus caret to the right side of 'A'
(5) Press key 'b'

What is the expected output?
'A' get underlined, and 'compositionstart' event should be fired on step (4).

What do you see instead?
'A' get underlined, but no 'compositionstart' event was fired on step (4). Instead 'compositionupdate' was fired on step (5) directly.

FireFox fires 'compositionstart' on step (4).

---

I believe the cause is:
  1. IME calls |InputMethodController::setCompositionFromExistingText()| on step (4), no events was fired but |m_hasComposition| was set to true.
  2. Following calls to |InputMethodController::setComposition()| won't fire 'compositionstart' since |m_hasComposition| is already true.

I can fix this if we can confirm this is indeed a bug.
Screenshot_20161027-160202.png
178 KB View Download

Comment 1 by aelias@chromium.org, Oct 27 2016

Cc: yabinh@chromium.org changwan@chromium.org
Yes, I agree this is a bug.

Comment 2 by yosin@chromium.org, Oct 4 2017

Labels: Pri-3

Comment 3 by chongz@chromium.org, Jan 11 2018

Cc: chongjiang@chromium.org rlanday@chromium.org

Comment 4 by chongz@chromium.org, Jan 11 2018

Cc: -chongjiang@chromium.org chongz@chromium.org
Owner: ----
Status: Available (was: Assigned)
Un-assigning myself.
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 14

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment