Another thing that happens is that when you open the settings editor. Then open the keyboard shortcuts and try to type in the input of the keyboard shortcuts nothing happens. The input of the settings editor is instead updated even though the keyboard shortcuts pane is focused.

In fact something weird happens. There is an edit context associated to the settings editor input which sends text update events. When we switch to the keyboard shortcuts editor and type int the input, despite the keyboard shortcuts input being clearly focused, the settings editor edit context keeps firing text update events. This can be seen in the following screen recording, where I record on the text update event, the currently focused element (which is the keyboard shortcuts input) and the dom element corresponding to the edit context which is currently firing the text update event (here it is the settings editor).

This seems to happens with the quick pick as well as with the search widget. These all share a common point in that they use the InputBox widget.

This issue does not reproduce on https://insiders.vscode.dev which is on the chromium version of your browser (so for me on the latest). This seems to be a chromium bug that we are seeing because we are on Electron 30.

I have used the google bisect tool and found the last revision with the bug and the first revision with the fix, namely:

1317063 (known bad)
1317085 (first known good)

After checking the URL: https://chromium.googlesource.com/chromium/src/+log/8850873881a39a3a4c0f1b2fec31c1256de54f66..396f34f201afa06c5530d4e0cf12a91c19847352

The commit that fixes the issue seems to be:

https://chromium.googlesource.com/chromium/src/+/3ee998b6e2fc6705ff40365ec5f5aad93a92b39d

cc @deepak1556

This issue will be closed.

Thanks for the bisect, the commit was first merged into 128.0.6548.0 which will be available with our Electron 32 version bump next month