feat(dashboard): make Galaxy browse and watch accessible
This commit is contained in:
@@ -0,0 +1,61 @@
|
||||
# Keyboard, search and touch browse validation
|
||||
|
||||
MX-01, MX-03 and MX-07 implemented against the actual BrowsePage and recursive
|
||||
BrowseTreeNodeView. Existing lazy projection, search index/debounce/cap,
|
||||
subscription deduplication, read scope, cancellation and live-read paths are retained.
|
||||
Only synthetic cached Galaxy metadata and redacted fake reads were exercised here.
|
||||
No COM, SQL, worker, LDAP or live key/session operation was involved.
|
||||
|
||||
Each expandable node has one native named button, explicit expanded state and a
|
||||
stable controlled container. Leaf objects do not advertise unavailable expansion.
|
||||
Explicit Watch actions on hierarchy attributes and search hits call the same
|
||||
AddTagAsync path as the retained mouse accelerators. A second Watch does not add
|
||||
another subscription. Visible introductory copy now makes Watch the primary path.
|
||||
|
||||
The search has a persistent visible label, cached-metadata boundary hint and
|
||||
controlled-results relationship. Its caller-owned polite result summary follows
|
||||
user searches, not the two-second value poll. Clear search cancels the existing
|
||||
search through its established setter and restores input focus after render.
|
||||
Search does not touch watched values; no-match/clear preserves subscribed rows.
|
||||
|
||||
Named focusable hierarchy/search/table regions contain long content. Full 207-character
|
||||
fixture references remain copyable and Watch stays at the tree's visible right edge.
|
||||
Remove actions name their full tag; a keyboard user can Tab from the named table
|
||||
scroller to a last-column action, which scrolls it into view. Pointer-coarse browse
|
||||
controls have 44 px minimum hit areas; desktop row sizes retain their compact geometry.
|
||||
The published Theme 1.0.1 supplies typography/tokens/focus; its package currently has
|
||||
no generic coarse-pointer sizing utility, so these domain-specific sizes remain local
|
||||
as allowed by the chapter's tree/control ownership. No shared-grid CSS was copied.
|
||||
|
||||
## Observed evidence
|
||||
|
||||
- Named expansion regression failed on the original generic toggle; leaf control
|
||||
case remained green. Search label/hint/control regression failed before the field
|
||||
contract. After implementation, 12 focused tree/search/projection/index tests pass.
|
||||
Framework HtmlRenderer remains; no bUnit dependency was added.
|
||||
- Actual synthetic routed fixture uses the production BrowsePage, recursive nodes,
|
||||
DashboardBrowseService projection and real DashboardBrowseSearchIndex. Its singleton
|
||||
cache/read providers are entirely in memory. The host now routes both native-dialog
|
||||
and browse fixtures through a standard Router and provides HeadOutlet.
|
||||
- One first batched inspection and one corrective confirmation cover 1440/1024/390px,
|
||||
real 200% zoom (720 CSS px/DPR 2), and coarse-pointer 390px. All five final workflows pass:
|
||||
keyboard expansion/Watch, repeated Watch with one row, preserved full long reference,
|
||||
search-hit Watch without duplicate, no-match/Clear/focus and retained subscriptions.
|
||||
Named scroller Tab reaches a full-context Remove action. No document overflow or
|
||||
browser page errors. See `evidence/browse-confirmation/results.json` and images.
|
||||
- The first touch-context request did not actually enable touch on this installed
|
||||
Chromium: navigator.maxTouchPoints remained 0 and pointer:coarse was false. This
|
||||
is visible in the first JSON and was not accepted as touch proof. Explicit browser
|
||||
CDP touch emulation then establishes maxTouchPoints 1 and pointer:coarse=true.
|
||||
`coarse-before.json` reproduces 19.7 px node/27.5 px Watch/Remove heights. The final
|
||||
actual coarse mode reports 44 px heights; its primary expand/Watch/Clear path uses
|
||||
touchscreen tap events. No CSS-only media override or screenshot relabeling.
|
||||
- First/corrective screenshots were inspected together. The correction names scroll
|
||||
regions, keeps Watch visible for long rows and expands only coarse-pointer targets.
|
||||
Full gateway regression testing remains at the chapter phase boundary; current
|
||||
evidence does not claim live COM/ACL integration or human screen-reader listening.
|
||||
|
||||
The shared Theme compatibility/native-dialog checkpoint is documented separately in
|
||||
`technical-light-dialogs.md`. Fault-first overview, remaining token/state cleanup,
|
||||
recoverable diagnostic behavior, rail vocabulary and shared Secrets release adoption
|
||||
remain separate chapter tasks; this browse checkpoint does not close them.
|
||||
Reference in New Issue
Block a user