New issue
Advanced search Search tips

Issue 826168 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

VK failed to commit backspace when input in console

Project Member Reported by iloahz@chromium.org, Mar 27 2018

Issue description

Chrome Version: 67.0.3376.0
OS Version: 10506.0.0

What steps will reproduce the problem?
(1) open a chrome console
(2) open VK, input several chars
(3) click backspace on VK, see shift state toggled
(4) click backspace on VK again, see text not been deleted

What is the expected result?
1. should not toggle shift state
2. should be able commit delete action

What happens instead?
as described in repro


 

Comment 2 by iloahz@chromium.org, Mar 27 2018

Owner: iloahz@chromium.org
Status: Started (was: Untriaged)

Comment 3 by iloahz@chromium.org, Mar 27 2018

Owner: shuchen@chromium.org
Cc: shuchen@chromium.org
Components: Platform>DevTools>Authoring
Owner: kozy@chromium.org
I suspect this might be an issue in DevTools text editor.

kozy@ can you please help to triage or narrow down the root cause? Thanks!

Components: -UI>Input>VirtualKeyboard
Confirmed the root cause is in DevTools.

1) The system receives the empty "text before cursor" after the Backspace deleted the tailing character. Somehow the input field might report the wrong selection range?
2) Due to the empty "text before cursor", the Virtual Keyboard switch to the SHIFT state and the following Backspace keydown event will carry the shiftKey=true modifier state. I can repro this by the physical keyboard: Backspace while holding Shift cannot delete character.

None of above related to the Virtual Keyboard or IME logic. So removed the VirtualKeyboard component.

Comment 6 by kozy@chromium.org, Mar 28 2018

Owner: einbinder@chromium.org

Sign in to add a comment