Skip to content

Panels page: group cards by the menu that opens them - #1307

Merged
enaboapps merged 3 commits into
mainfrom
panels-page-groups
Nov 3, 2026
Merged

enaboapps merged 3 commits into
mainfrom
panels-page-groups

Conversation

@enaboapps

@enaboapps enaboapps commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Closes #1306

The Panels page listed eleven built-in menu cards in one flat row, with the mouse panel and keyboard in a separate section, so nothing showed which menu opens which, and the page was busy.

Now:

  • My panels stays at the top as the page's main content, with the New panel button, as before.
  • Built-in menus and panels below is one row per menu or panel in two lists side by side, each under the menu that opens it: On Home (Home, Mouse panel, Keyboard, Apps and windows, Editing, Browser with Tabs indented under it, Media, Zoom) and On More actions (More actions, Mouse, Displays, Scanning). Menus on both Home and More are listed once, under Home, and say Also on More.
  • Row text and accessible names carry the place (Editing, not changed, also on More; Tabs, not changed, in Browser); the lists are named by their headings and the nested list is Inside Browser, so screen reader users get the same structure. Any menu kind the frontend does not know lands in an Other menus list rather than disappearing.
  • Closing the editor puts focus back on the row or card that opened it (found by id), falling back to New panel.

The browser fallback in api.ts gains Browser, Tabs, More actions and Displays so the lists show without the backend and in tests.

Docs: site/src/content/docs/using/panels.md describes the lists and the screenshot is recaptured.

Validation

  • npm run lint, npm test (356 vitest + 23 node), npm run build, site build: pass.
  • New tests: lists the built-in menus and panels under the menu that opens them (order, nesting, focus return) and keeps a menu it does not know where to place.
  • Dev build (npm run tauri dev) driven with Cua Driver: the Panels page shows the two lists with the rows named as above; opening Tabs and choosing All panels returns to the list.
  • No Rust changes.

🤖 Generated with Claude Code

Home comes first with the mouse panel, the keyboard and the menus Home
opens, Tabs listed inside Browser; then My panels with the New panel
button; then More actions with the three menus only it opens. Menus on
both Home and More are listed once, under Home, and say Also on More.
The browser fallback gains Browser, Tabs, More actions and Displays so
the groups show without the backend.

Closes #1306

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
site Ready Ready Preview Nov 3, 2026 9:11am UTC

Request Review

My panels stays at the top as the page's main content. The built-in
menus and panels become one row each in two lists, On Home and On More
actions, side by side, with Tabs indented under Browser, instead of
fifteen picture cards in three groups. Closing the editor puts focus
back on the row or card that opened it, found by id.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The docs intro now describes the page as it is: the user's panels first,
then Built-in menus and panels as two lists. Rows are called rows, the
page of clicks after a point is named as the one that cannot change,
the New panel button is the explicit focus fallback, and a nested menu
whose parent is missing falls to Other menus instead of vanishing.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@enaboapps
enaboapps marked this pull request as ready for review November 3, 2026 09:13
@enaboapps
enaboapps merged commit 380df99 into main Nov 3, 2026
10 checks passed
@enaboapps
enaboapps deleted the panels-page-groups branch November 3, 2026 09:18

This branch was successfully deployed

1 active deployment
Preview — 6e94cf11 Deployed Nov 3, 2026 by vercel[bot]
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.

Panels page: group cards by the menu that opens them

2 participants