CMODAL-108 · Make feedback durable

Reflow portal dialogs without hiding their confirmation actions

Practice briefBugIntermediate

Magnified text pushes Save below a fixed-height dialog with no reachable scroll path. Reflow the dialog shell.

Focused work estimate: 2h + prerequisites
Priority in the scenario: Medium
Engineering practice: CSS · Responsive design

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.

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.

Acceptance criteria

Content scrolls inside labeled region
Actions stay reachable
Document background remains inert

Implementation constraints

Avoid fixed pixel heights for text containers.

Verification to include

Check 200 percent text sizing
Use long error descriptions

Deliverables

Responsive dialog styles

Rollout and recovery

Use full-page forms if actions cannot remain reachable.

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.