CMODAL-103 · Specify overlay contracts

Define when unsaved settings dialogs may close

Practice briefTaskIntermediate

Escape silently discards edited settings. Add a dirty-state close contract shared by close button and outside interaction.

Focused work estimate: 2h + prerequisites
Priority in the scenario: High
Engineering practice: Forms · State machines

Estimated field mix

Frontend60%
Accessibility40%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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.

Use in my work board View project and downloads

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

Acceptance criteria

Clean dialogs close normally
Dirty close requests confirmation
Cancel keeps draft and focus

Implementation constraints

Avoid browser-wide beforeunload for local overlay changes.

Verification to include

Close clean dialog
Cancel dirty dismissal

Deliverables

Close policy and interaction cases

Rollout and recovery

Disable outside dismissal while correcting the policy.

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.