The next release of the IME should fix this problem.

Chrome Version: 65.0.3325.209
OS Version: 10323.67.0
Platform: Google Pixelbook in Tablet Mode, Stable Channel
Bugged On-Screen Keyboard: GB UK Keyboard

What steps will reproduce the problem?
1. In Tablet Mode, tap anywhere that takes text input (eg: Chrome browser address field; Evernote Android app in editing mode) to open the on-screen keyboard
2. If necessary, switch to the Full Layout keyboard
3. Tap on the 'caps lock' key, to try to toggle caps lock on and off

What is the expected result?
The 'caps lock' key only toggles caps lock on and off, without outputting any text

What happens instead of that?
Each time the 'caps lock' key is tapped, the word "Unidentified" is output into the text that is being typed. For example:
● what I want: "The warning DANGER appears"
● what I now get: "The warningUnidentified DANGERUnidentified appears"

Did this used to work correctly?
Yes: in Chrome OS 62, 63, and 64 - the 'caps lock' key only toggled caps lock on and off, without outputting "Unidentified" every time.

When did this bug first show up?
Immediately after updating to Chrome OS 65, which happen for me yesterday, Thu 05 Apr 2018.

Is there a workaround?
Yes: as reported in...
● 'On-screen keyboard Caps Lock error message?'
» https://productforums.google.com/forum/#!topic/chromebook-central/FBvAbDqJXyg
...tapping on the 'alt' key immediately before and after tapping on the 'caps lock' key inhibits its newly bugged behavior, preventing the unwanted "Unidentified" text from being output. Now I have to tap 'alt', 'caps lock', 'alt' on every occasion when I just want to toggle caps lock on or off again!

From my experience, as documented in Comment 3 above, this Brand NEW Inconvienience was ADDED to Chrome OS by the OS development team in the Chrome OS 65 update to the supposedly "Stable" channel.

In buying in to the Chrome OS platform for the first time, by buying Google's supposedly "flagship" Pixelbook & Pen four months ago, and staying in the supposedly "Stable" Chrome OS channel, I naively assumed that Chrome OS would actually IMPROVE over time - but the naivety of this assumption is attested to by the fact that this is the THIRD example of a Chrome OS update DEGRADING my UX (the others being having the side shelf option in Tablet Mode REMOVED, and the Pixelbook Pen becoming context-menu-phobic).

Q1. WHY does the Chrome OS "development" process regularly produce a DEGRADED user experience in the supposedly "Stable" channel?

@jzfeng@chromium.org - thank you for letting us know that "The next release of the IME should fix this problem", but you failed to say WHEN this will occur.

Q2. WHEN will this new developer-created BUG actually get FIXED?

Sorry for the inconvenience.

@wuyingbing: do you have an idea when the new release get pushed, or can we do something to push the fixed version as soon as possible?

Thanks!

An incremental update to Chrome OS 65 arrived today - specifically: Wed 18 Apr 2018, Google Chrome: 65.0.3325.209 (Official Build) (64-bit), Platform: 10323.67.0 (Official Build) stable-channel eve - but this novel and annoying 'caps lock key types Undefined' bug, introduced by the Chrome OS development team into Chrome OS 65, still remains unfixed.

So I need to ask again...

Q. WHEN will this new developer-created BUG actually get FIXED?

The fix is applied on M67, however, I don't how to merge back M65.

This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop)

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

merge approved

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/1509defd79b3ef25e5f10a1a0cf53abcecad492a

commit 1509defd79b3ef25e5f10a1a0cf53abcecad492a
Author: Yingbing Wu <wuyingbing@google.com>
Date: Thu Apr 19 07:12:26 2018

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

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