Keep pending portal dialog saves cancellable without duplicate writes
A slow save invites repeated clicks and users cannot tell whether closing cancels the write. Specify operation and view lifecycles separately.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Concurrency · Failure semantics
Estimated field mix
- Frontend60%
- API design40%
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 membership portal Juniper manages synthetic team settings. Use locally owned components and a local settings adapter.
Setup prerequisites
- Create synthetic settings forms and destructive-action stubs.
- Provide delayed success, rejection and removed-trigger cases.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CMODAL-101 · Name team-setting dialogs from visible headings
- CMODAL-103 · Define when unsaved settings dialogs may close
- CMODAL-104 · Return focus when a portal dialog trigger disappears
- CMODAL-105 · Keep parent settings inert while a nested confirmation is open
- CMODAL-106 · Prevent menu dismissal from swallowing a settings action
Acceptance criteria
- One pending write per revision
- Closing does not claim server cancellation
- Reopen reconciles operation status
Implementation constraints
- Adapter cancellation may be advisory only.
Verification to include
- Close after accepted save
- Timeout then reopen same operation
Deliverables
- Pending-operation model and races
Rollout and recovery
Disable closing during unresolved operations with an explicit explanation.
Value of the work
For the engineer: Practice focus containment, dismissal and asynchronous feedback.
For the team: Inspect whether shared UI primitives protect users across many product flows.
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.