Change:
inputBoxStyles: defaultInputBoxStyles }); <del> const disposables = new DisposableStore(); const _onDidAccept: Emitter<void> = disposables.add(new Emitter<void>()); const onDidAccept: Event<void> = _onDidAccept.event; const _onDidReject: Emitter<void> = disposables.add(new Emitter<void>()); const onDidReject: Event<void> = _onDidReject.event; const hideInputBox = () => { element.classList.remove('input-mode'); container.style.paddingLeft = '10px'; }; disposables.add(DOM.addStandardDisposableListener(whenInput.inputElement, DOM.EventType.KEY_DOWN, e => { </del> <ins> this._register(DOM.addStandardDisposableListener(this.input.inputElement, DOM.EventType.KEY_DOWN, e => { </ins> let handled = false; if (e.equals(KeyCode.Enter)) { <del> hideInputBox(); _onDidAccept.fire(); </del> <ins> this._onDidAccept.fire(this.input.value); </ins> handled = true; } else if (e.equals(KeyCode.Escape)) { <del> hideInputBox(); _onDidReject.fire(); </del> <ins> this._onDidReject.fire(); </ins> handled = true; } if (handled) {

Discussion:
Follow up from I have a completion item provider for context keys. For the keybindings UI this isn't working yet and what's needed is the simple editor widget as the input when authoring when-clauses a similar completion item provider (using internal API) that uses the same data source ()
Started using (Code Editor) for when input and I am seeing following issues with the code editor widget is showing far away from the editor. <img width="858" alt="image" src="https://user-"listen on key and accept the when text. This is causing problem when I am accepting an option from suggest list using Enter. Is there a way to prevent this to happen? / Your expertise would be very helpful here. You can find changes here -
Pretty sure that you need to use the keybindings service instead, e.g don't listen to keydown/up event directly ops... that seems very wrong, both widgets are normal content/overlay widgets
Right. I am using keybindings to accept/reject when expression changes. And it fixed the second issue. Thanks. Issue with suggest widget is only pending.
Investigated the issue with overflow content widget misplacement and here is what I found: This seems to be a bug with editor overflowing content widget value set to . According to the docs, when position value is set to fixed then the position of the element will be relative to its containing block, which is In keybindings editor, the table widget (extending list widget) has the ancestor rows element with and css property set. Hence overflowing content widgets are drawn relative to the table rows element. This can be confirmed by disabling the on the table widget that does not set above css properties. This means, embedding a code editor widget inside any node that has these css properties set will break the position of the overflowing content widgets CC / for editor related. CC for table/list related. Can you please let me know what is the right way to proceed here. Does it makes sense to disable for keybindings table? Or this shall has to be fixed in editor?
It seems the trick is to use option in the code editor. But it seems to work only for content widgets but not for overlay widgets - like suggest element details. Using the same for overlay widgets fixes it.

For now disabled table transformations and created a separate PR to fix it in the editor -
Verify that while editing when column in keyboard shortcuts editor shows the list of context key suggestions.
I see this is implemented but it's also mostly broken because it doesn't work with prefixes