Skip to content

fix(app): forward ⌘L from a focused browser page to the address field - #57965

Merged
kitlangton merged 1 commit into
betafrom
side-panel-cmd-l
Oct 22, 2026
Merged

kitlangton merged 1 commit into
betafrom
side-panel-cmd-l

Conversation

@kitlangton

@kitlangton kitlangton commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

What

⌘L (Ctrl+L on Windows and Linux) now focuses and selects the side panel browser's address field while keyboard focus is in the page. Before, pressing it there did nothing.

How

The page now hands ⌘L to the pane the same way it already hands over ⌘T and ⌘W. pageShortcut claims it, main forwards it to the window, and the pane dispatches it inside #browser-panel. There, the existing scoped browser.address command answers it. So ⌘L takes the same route in the page as on the pane's own surface.

The dedicated address pane event that used to carry ⌘L from the page is removed (chromium.ts, pane.ts, ipc.ts, connection.ts, model.ts, panel.tsx). That leaves one route for every forwarded chord.

Unchanged

  • Outside the browser pane, ⌘L does nothing on macOS. On Windows and Linux, Ctrl+L still focuses the composer.
  • ⇧⌘L still goes from the page to the shell, as before.

Tests

  • keys.test.ts: ⌘L and Ctrl+L are forwarded, including on Dvorak (L on the physical P key).
  • browser-pane-restore.spec.ts: new story. ⌘L is pressed in the page, then on the pane's surface, and must select the whole URL each time. Pressed in the main column, it must leave the address alone.

Known limit

Like ⌘T and ⌘W, the page only forwards the default chord. If the address command is rebound, the page still claims ⌘L, but nothing answers it.

Base automatically changed from side-panel-focus to beta October 21, 2026 23:42
@kitlangton
kitlangton merged commit e8f0b3e into beta Oct 22, 2026
9 of 17 checks passed
@kitlangton
kitlangton deleted the side-panel-cmd-l branch October 22, 2026 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant