New issue
Advanced search Search tips

Issue 774568 link

Starred by 1 user
Status: Duplicate
Merged: issue 775743
Owner: ----
Closed: Oct 2017
Cc:
jamiewa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug-Regression

Blocked on:
issue 775743


Sign in to add a comment

CapsLock gets "stuck" on in Chrome Remote Desktop Linux host, until focus switched

Project Member Reported by w...@chromium.org, Oct 13 2017 
Chrome Version: ChromeOS 62.0.3202.43, Client CRD 61.0.3163.20
, Host CRD 61.0.3163.20
OS: ChromeOS Panther

What steps will reproduce the problem?
(1) Connect to a Linux host.
(2) Type some stuff.
(3) Press Caps Lock, and type more.
(4) Press Caps Lock, and type more.
(5) Switch to another window, then back again, then type more.

What is the expected result?

At #4 expect the typed text to be lower-case.

What happens instead?

At #4 the text is still upper-case.
At #5 the text is lower-case again.

Comment 1 by jamiewa...@chromium.org, Oct 17 2017 

It sound like the CapsLock state is not being reported correctly. It's not an ideal test because it doesn't use Pepper, but can you see if the correct state is reported for the CapsLock modifier at http://w3c.github.io/uievents/tools/key-event-viewer.html?

Comment 2 by w...@chromium.org, Oct 17 2017 

Using the W3C event viewer I see the modifier state set correctly, but the
keydown/keyup events for CapsLock are a complete mess.

Comment 3 by w...@chromium.org, Oct 17 2017

Blockedon: 775743
Based on #2, believe this is caused by ChromeOS regression  issue 775743 .

Comment 4 by jamiewa...@chromium.org, Oct 19 2017

Mergedinto: 775743
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment