Skip to content

Visor: keyboard navigation, mobile rows, and legibility - #182

Merged
lannbot merged 2 commits into
mainfrom
evaluate-visor-ui-ux
Sep 8, 2026
Merged

Visor: keyboard navigation, mobile rows, and legibility#182
lannbot merged 2 commits into
mainfrom
evaluate-visor-ui-ux

Conversation

@lannbot

@lannbot lannbot commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Fix UI review findings 1, 3, and 8: explicit drawer dismissal and Escape, focus transfer/return, inert app and outgoing panes, and named unsaved-change confirmation that preserves its pending action.
  • Constrain device identifiers to keyboard-accessible local scrolling and wrap status rows at 320px/390px without overlap.
  • Keep the saturated identity palette with high-contrast dark strip text, 44px control heights, visible focus rings, clearer section headings, and bounded desktop inputs.
  • Add five Chromium regression scenarios covering keyboard/dialog behavior, reduced motion, narrow layouts, identifier readability, and all 360 hues.

Verification

  • Astra review completed, including a reproduced and corrected scrim/confirmation action-replacement bug.
  • just check passed.
  • just test passed (156 Rust tests plus Deno suites).
  • just e2e passed (27 scenarios) after merging current main's app-install changes.
  • Additional Chromium probes confirmed Escape restores the edited input, scrim clicks do not replace a pending sheet switch, and desktop fields are bounded at 384px.

Automerge will be armed with merge commits. Browser verification uses real Chromium; physical mobile devices and other browser engines were not tested.

@lannbot
lannbot enabled auto-merge September 8, 2026 04:12
@lannbot
lannbot merged commit 433ca5b into main Sep 8, 2026
2 checks passed
@lannbot
lannbot deleted the evaluate-visor-ui-ux branch September 8, 2026 04:18
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