Keep report details discoverable after virtualized rows leave view
Expanded row details unmount during scrolling and leave focus nowhere. Bound virtualization around active interaction.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Virtualization · Focus management
Estimated field mix
- Accessibility40%
- Performance engineering30%
- 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
Fictional cooperative Quarry reviews synthetic service-volume reports. Build local report fixtures with empty, missing and delayed values.
Setup prerequisites
- Create synthetic report series with explicit missing values.
- Stub report loading, sorting and export responses.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CTABLE-102 · Preserve table header associations in the reporting workbench
- CTABLE-101 · Give report charts a textual trend summary
- CTABLE-103 · Represent missing report observations distinctly from zero
- CTABLE-104 · Expose report sorting through semantic header buttons
- CTABLE-105 · Keep report filter errors near their controls
- CTABLE-106 · Provide a keyboard alternative to chart range brushing
Acceptance criteria
- Focused details remain mounted
- Collapsed rows release retained nodes
- Large fixtures stay within documented DOM budget
Implementation constraints
- Do not pin every previously opened row forever.
Verification to include
- Scroll focused detail out of view
- Collapse and verify reclamation
Deliverables
- Focus-aware virtualization policy
Rollout and recovery
Disable virtualization for interactive details if focus is lost.
Value of the work
For the engineer: Practice semantic data presentation and robust interaction.
For the team: Inspect whether reporting decisions remain possible without color or pointer use.
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.