Make critical portal notifications persistent until acknowledged
A failed permission change disappears after four seconds. Separate persistent actionable failures from transient informational status.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Live regions · Error handling
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 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-102 · Make portal notification dismissal keyboard operable
- 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
- CMODAL-107 · Keep pending portal dialog saves cancellable without duplicate writes
Acceptance criteria
- Failed changes remain visible
- Acknowledgement is explicit
- Repeated same failure coalesces without losing action
Implementation constraints
- Do not use urgency announcements for every toast.
Verification to include
- Reject permission change
- Repeat rejection and inspect coalescing
Deliverables
- Notification priority contract
Rollout and recovery
Disable auto-dismiss for all actionable messages if classification fails.
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.