Define keyboard entry and escape for inventory cells
Arrow keys sometimes move cells while users edit text. Introduce explicit navigation and editing states.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Accessibility · Keyboard
Estimated field mix
- Accessibility60%
- Frontend40%
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Enter starts editing
- Escape restores committed value
- Editor arrows retain native behavior
Implementation constraints
- Provide semantic controls and visible focus.
Verification to include
- Edit without a pointer
- Escape an invalid draft
Deliverables
- Keyboard contract and checks
Rollout and recovery
Fall back to ordinary row forms.
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.