Keep inventory column widths after reload
Operators resize the SKU column every morning. Save bounded widths per grid version.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Browser storage · Layout
Estimated field mix
- Frontend100%
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 supplier Reedworks uses a browser inventory table. Quantities are planning records, not live warehouse instructions.
Setup prerequisites
- Create synthetic SKUs with revisions and nullable quantities.
- Implement a local paginated adapter with conditional updates.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Widths restore after reload
- Limits prevent hidden controls
- Reset removes overrides
Implementation constraints
- Persist layout only.
Verification to include
- Restore two widths
- Corrupt saved JSON and verify defaults
Deliverables
- Width persistence and reset control
Rollout and recovery
Disable persistence if controls disappear.
Value of the work
For the engineer: Practice grid interaction and concurrent edit recovery.
For the team: Inspect how changes protect operator intent during partial failures.
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.