2.1 KiB
2.1 KiB
Chat UI clarity follow-up
Addresses the independent screenshot review of the populated chat workspace.
- Mobile inactive panes have a persistent chat title and explicit Switch action, a divider grip, and a separate transcript viewport. Remembered peek bounds and Tape default are preserved.
- Code blocks and tables expose actual horizontal overflow with native persistent scrollbars, a directional cue, keyboard focus/arrows and semantic actions.
- Chat headers reserve their own viewport rather than covering scrolling content. Model and permission values remain readable in narrow panes and with enlarged text. Exceptionally short headers scroll to keep controls reachable.
- Chat identity colors remain stable; Active/Visible and Working/background/New are separate textual or shaped states. Compact rows retain attention badges, identity initials and full-context tooltips. Tested metadata/state contrast is at least 4.5:1 across 64 native palette/identity combinations; this is not a complete accessibility audit.
- Main navigation has captions. Compact chat navigation exposes a labeled Menu with all destinations and returns without discarding chat state or drafts. Caption taps preserve text-field focus.
Verification
- Integration: 1,578 tests passed across chat, settings, motion, adaptive UI,
shell and application (
/tmp/memwatch/out.ouMreH). - Final header/text-scale and caption-focus changes: 13 tests passed
(
/tmp/memwatch/out.EtZ7az). Final analyzer clean (flutter-analyze.TyE0Cf). - Real browser full-app fake-gateway captures: Material dark mobile and desktop, Material light desktop and Cupertino light mobile. Compact Menu navigation, Tape switching and inactive transcript bottom were exercised. Fixtures only; no real chats or runs were modified.
- Captures:
/tmp/review/chat-clarity-desktop-reviewed,/tmp/review/chat-clarity-light,/tmp/review/chat-clarity-phone,/tmp/review/chat-clarity-cupertino. - No native device test or installation was performed. The personal Fold remains delivery-only. Web and APK deployment are tracked separately from code checks; these client changes require no server restart.