Note
Grok responding on behalf of Julius.
Triage
Thanks for the clear repro and the source pointers, @SherzodAli! This matches current main (7812230572f2), and no duplicate turned up. There turn out to be two separate things in here.
What I found
sidebar.toggle(mod+b) andrightPanel.toggle(mod+alt+b) are hostwindowlisteners inAppSidebarLayout.tsxandChatView.tsx. The URL bar and panel header live in that document, so the keys work there, but a focused<webview>page is a separate process whose keys never reach those listeners.- The guest's
beforeInputhandler only claims the refresh chord, andsetIgnoreMenuShortcuts(true)keeps other keys away from the application menu. The test "keeps preview shortcuts out of the host window" covers chords likemod+k,mod+j, andmod+w. - Forwarding every binding without
when: previewFocuswould have side effects: from the host, the focused element is the<webview>, soeditableFocusis false even while typing in the page. For examplemod+zwould undo a thread action, andmod+bwould toggle the sidebar instead of bolding text in a page editor. rightPanel.toggleMaximizedis a separate problem. It's a bindable command and the header button callstoggleRightPanelMaximized, but no keydown handler dispatches it, so a custom binding does nothing even when the chat has focus.
Likely fix area
- The maximize binding: the
ChatViewkeydown handler, next torightPanel.toggle. - Layout chords from a focused page: this overlaps with open PR #15035, which forwards browser-style chords from the guest and currently leaves panel toggles with the page. Options include forwarding a specific allowlist of layout chords from
beforeInput, or keeping them with the page.
A maintainer will decide on the fix direction.