Skip to content

Open maximised and lay pages out for wide windows - #1000

Merged
enaboapps merged 2 commits into
mainfrom
claude/maximised-layout
Oct 7, 2026
Merged

enaboapps merged 2 commits into
mainfrom
claude/maximised-layout

Conversation

@enaboapps

@enaboapps enaboapps commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Closes #999

What

  • Maximised on launch: tauri.conf.json sets the main window to maximized: true. Restoring or resizing afterwards is respected, and the existing size and minimum size still apply when restored.
  • Wider pages: the fixed 1100px page column becomes min(100%, 1760px), with padding that scales with the window.
  • Wide layout: from 1200px of page width (a container query on .view, so it responds to the page, not the screen):
    • Settings sections (Settings tabs, Switches, Scanning, Mouse) put their title and description in a left column, sticky while scrolling, with the controls on the right capped at a usable width. Toggles and choice groups no longer stretch across the whole monitor.
    • Lists of rows (Home status, Help setup and troubleshooting, Switch Forwarding profiles) become a two-column grid of tiles inside the same card, with hairlines between tiles. Single-row cards are unaffected.
    • Account: the band spans the full width, Settings sync and Delete account stack on the left, and What syncs sits beside them.
    • Tabs size to their labels instead of stretching across the page.
    • Scanning drops its separate 920px cap. Its intro paragraph keeps an 80ch reading width, and other paragraphs keep their existing max-widths.
  • Smaller windows (including a maximised 1366px laptop) keep the single-column layout, and the compact layout under 800px is unchanged.

Review fixes

  • Named page container: the page is a named container (page), so every wide rule, including tile borders inside lists that are containers themselves, measures the page.
  • Reading width: notes outside setting groups keep an 80ch width, and Scanning's More options content is capped at 1040px.
  • Account alignment: the cards line up, and What syncs spans two rows only when there are two cards beside it.
  • Unused rule: removed.
  • Product note: window state isn't remembered, so the app opens maximised on every launch even if it was restored last time.

Validation

  • npm run lint, npm test (290 passed) and npm run build.
  • Visual: every page rendered at 2048, 1366 and 920px wide, in headless Chrome against the dev server with the native bridge mocked. Checked Home, Switches, Scanning, Mouse, Mobile, Switch Forwarding, all Settings tabs, Help (both tabs) and Account.
  • The real app (dev build on Windows) opened maximised on a 2048×1104 screen, confirmed by computer use.

🤖 Generated with Claude Code

The main window opens maximised. Pages drop the fixed 1100px column (now
up to 1760px), and from 1200px of page width settings sections put their
title beside their controls, lists of rows (Home, Help, Switch Forwarding)
become two columns of tiles, the Account page sets What syncs beside its
actions, and tabs stop stretching. Paragraphs keep their reading width,
and smaller windows keep the single-column layout.

Refs #999

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@enaboapps enaboapps added this to the v1.0.0-rc.22 milestone Oct 7, 2026
Address review on the wide layout:
- Name the page container so every wide rule (including tile borders
  inside lists) measures the page, not an inner list.
- Notes outside setting groups keep an 80ch reading width, and Scanning's
  More options content keeps a usable width.
- Align the Account cards, and only stretch What syncs across two rows when
  there are two cards beside it.
- Drop a rule that never matched.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@enaboapps
enaboapps marked this pull request as ready for review October 7, 2026 11:31
@enaboapps
enaboapps merged commit 583ce67 into main Oct 7, 2026
6 checks passed
@enaboapps
enaboapps deleted the claude/maximised-layout branch October 7, 2026 12: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.

Open maximised and let pages use the available width

2 participants