cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

test(ui): qualify flat application layouts and keyboard focus

Browse Source
This commit is contained in:
cesnimda
2026-11-04 01:06:13 +01:00
parent c9138af01e
commit 1c88cacb4d
221 changed files with 4724 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ui-modernisation/visual-correction/APPLICATION_FLAT.md
+3 -1
View File
@@ -15,6 +15,8 @@ Browser evidence is deliberately distinct: `applications-flat` is the successor
Successor update: the older non-focused run completed180 states but cannot close the focus gap; retained as `PREDECESSOR-180.json` without claiming an immutable source manifest or using it for final qualification. Focus correction export built successfully; the new six-state phone pilot passed, including an explicit visible/unclipped row outline assertion. Final36-config/216-state run is next. Types/build and full lint passed for this correction. Do not add pilot/predecessor results to final totals.
Remaining work: run full216, inspect phone/tablet/desktop and EN/NB/dark expanded detail captures, review source/evidence identities, publish/read back validated source and evidence checkpoints. Backend/physical PDF/provider/model/native/final security/release qualifications remain separate. Only app chrome changed; do not reopen accepted physical PDF metrics without an affected renderer change.
PASSED successor:36 configurations /216 scans and screenshots /36 controlled journeys,36 visible-outline checks and zero clipped phone outlines, violations, unexpected writes or browser errors.36 status writes were fixture responses. Runtime source checkpoint is `c9138af01e6dd7cc407a9b71c921914d8c1299f0`. The pilot and predecessor are not additive. Manual inspection sampled final1440 desktop detail and390 NB/dark focused list, confirming open sections, preserved right-side context, labelled direct actions and fully visible focus outline.
Remaining work: freeze source/evidence identities and publish/read back this bounded checkpoint; continue account and remaining route review. Application chrome now has substantially flatter hierarchy, but final visual acceptance and any further title/filter-density discrepancies remain separate. Backend/physical PDF/provider/model/native/final security/release qualifications remain separate. Only app chrome changed; do not reopen accepted physical PDF metrics without an affected renderer change.
Next eligible packages after this bounded correction: account continuous sections (V10), remaining route visual review/connected workflows, and the bounded literal-date localisation defect (V11). Whole34-route/57-group acceptance and final owner review remain OPEN. No orchestrator, main merge, production or deferred import-engine work.