noCV
CMODAL-105 · Handle nested interactions

Keep parent settings inert while a nested confirmation is open

Practice briefBugAdvanced

Tab reaches the parent form behind a confirmation dialog. Compose modal ownership across one nested level.

Focused work estimate
3h + prerequisites
Priority in the scenario
High
Engineering practice
Accessibility · Modal composition

Estimated field mix

  • Accessibility70%
  • Frontend30%

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.

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.

Acceptance criteria

  • Tab stays in active confirmation
  • Escape closes only top layer
  • Parent state survives confirmation cancellation

Implementation constraints

  • Use the accessible primitive rather than manual document-wide traps.

Verification to include

  • Cycle Tab through nested dialog
  • Cancel then resume parent form

Deliverables

  • Nested-dialog composition tests

Rollout and recovery

Replace nested confirmation with an inline confirmation step.

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.