Handle access loss without an empty-reader trap
Access expires while a reader is on a late section. The next fetch clears the page and leaves focus on a removed annotation button.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization UX · Cache isolation · Focus recovery
Estimated field mix
- Security40%
- Accessibility30%
- Frontend30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Plainview handbook reader serves versioned HTML documents with headings, tables, footnotes, and annotations. Scope is accessible HTML rendering from a structured model; OCR and arbitrary PDF remediation are excluded.
Setup prerequisites
- Versioned synthetic documents with stable section IDs
- Annotation and document-access API contracts to stub
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- READ-101 · Restore heading and table semantics in handbook chapters
- READ-102 · Let readers adjust text without losing their place
- READ-104 · Keep contents links and footnote returns oriented
- READ-107 · Load long handbooks without losing reading order
- READ-103 · Navigate search matches without breaking document text
- READ-105 · Recover bookmarks after a handbook correction
- READ-106 · Render annotations safely and expose their controls
- READ-108 · Keep annotation review stable through collaborator updates
Acceptance criteria
- Confirmed access loss stops fetches and clears protected rendered content.
- Focus moves to a named access-state heading with permitted navigation.
- Account changes cannot restore prior content through cached sections or Back.
Implementation constraints
- Omit private authorization details and document account-scoped draft handling on access loss.
Verification to include
- Remove access during a section fetch and verify a useful accessible access state.
- Switch account and navigate Back; protected cached content stays absent and stale fetches stop.
Deliverables
- Access-loss boundary and account-switch browser tests
Rollout and recovery
Verify before enabling protected handbooks; disable protected caching if invalidation cannot be guaranteed.
Value of the work
For the engineer: Practice semantic structure, accessible navigation, safe annotations, and stable reading positions.
For the team: Inspect how an engineer makes information usable while protecting document integrity and access boundaries.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.