Skip to content

Restore titlebar double-click with hidden tab strip - #1867

Merged
raphamorim merged 3 commits into
mainfrom
titlebar-chrome
Aug 12, 2026
Merged

Restore titlebar double-click with hidden tab strip#1867
raphamorim merged 3 commits into
mainfrom
titlebar-chrome

Conversation

@raphamorim

Copy link
Copy Markdown
Owner

Supersedes and closes #1866 by @jxdones, keeping their commit. The original fix is right: on macOS with hide-if-single, the full-size content view keeps the top band as custom window chrome (padding_top_from_config reserves ISLAND_HEIGHT whenever Tab navigation is enabled), so clicks there belong to the window drag and double-click handler, not the grid.

On top of it, the two review notes applied:

  • The chrome-band predicate now lives in one place. Navigation::chrome_band_reserved encodes "macOS reserves the band whenever Tab navigation is enabled, other platforms only while the island is painted", and both input layers (the cursor override in application.rs, the click routing in screen/mod.rs) call it instead of re-deriving the condition. It must agree with padding_top_from_config, and the doc comment plus a unit test pin that contract.

  • Right-clicks in the hidden band are consumed like the visible island's chrome regions instead of falling through to the grid, where they acted on the first terminal row while the pointer was over window chrome.

The UCRT64 failure on the original PR was our CI lane building workspace cdylibs in debug, which exceeds the PE export-ordinal limit on windows-gnu; fixed on main and this branch includes it.

@raphamorim
raphamorim merged commit ba41255 into main Aug 12, 2026
3 of 4 checks passed
@raphamorim
raphamorim deleted the titlebar-chrome branch August 12, 2026 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants