New issue
Advanced search Search tips

Issue 898108 link

Starred by 2 users
Status: Assigned
Owner:
shuchen@chromium.org
Cc:
wuyingbing@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

IMF doesn't fire onFocus event when the focus is switched among the same type of input fields

Project Member Reported by wuyingbing@chromium.org, Oct 23 
Chrome Version: (copy from chrome://version)
OS: ChromeOS M71, M72

What steps will reproduce the problem?
(1) open myinputdemo.appspot.com/inputboxes.html
(2) switch focus between "text" and "text2" input boxes.

What is the expected result?
IMF should fire onBlur and onFocus events.

What happens instead?
IMF only fire onRest events.



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.

Comment 1 by shuchen@chromium.org, Oct 23 

This is issue related to chrome.inputMethodPrivate.onFocus or chrome.input.ime.onFocus?

Comment 2 by robliao@google.com, Nov 1

Labels: Hotlist-DesktopUIConsider

Comment 3 by robliao@google.com, Nov 1

Labels: -Hotlist-DesktopUIConsider

Comment 4 by wuyingbing@chromium.org, Nov 14 

Issue 899408 has been merged into this issue.

Comment 5 by shuchen@chromium.org, Nov 14

Cc: wuyingbing@chromium.org
Labels: -Pri-1 -M71 -M72 Pri-3
Status: Assigned (was: Untriaged)
Summary: IMF doesn't fire onFocus event when the focus is switched among the same type of input fields (was: IMF doesn't fire onFocus event)
Updating the title to reflect the real issue.

This issue only happens when the focus is switched among the same type of input fields in the web page.

Note: this bug is NOT a regression.

Comment 6 by jmukthavaram@chromium.org, Nov 15

Labels: OS-Chrome

As per above details issue seems to be specific to chrome OS hence adding the same.
►

Sign in to add a comment