Chrome Version: Since at least 59.0.3071.134 (60.0.3112.112 also repros)
OS: ChromeOS

What steps will reproduce the problem?
(1) Remap Search to CapsLock
(2) Visit http://w3c.github.io/uievents/tools/key-event-viewer.html
(3) Press and release CapsLock a few times.

What is the expected result?
Each press and release of CapsLock should give two events; a keydown followed by a keyup.

What happens instead?
A single keydown event is generated in both cases.

This appears to be a recent regression and impacts Chrome Remote Desktop particularly badly, since it relies on accurate keyboard events in order to synchronize the local and remote lock states.