Prevent accidental backdrop clicks from discarding input

What to change

Ask the supplier to make outside-click dismissal appropriate to the dialog's purpose and the amount of unfinished work it contains.

A worked example

Illustrative example

An unfinished callback request remains open after a stray tap outside its panel, while an explicit Cancel action offers a clear way to leave.

How to check the result

Accept when accidental backdrop interaction cannot silently destroy substantial work and deliberate dismissal remains straightforward.

A mistake to avoid

Disabling all dismissal routes except an obscure corner icon can prevent data loss while making the dialog unnecessarily difficult to escape.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordOpen a dialog containing editable fields and enter fictional information. Tap the backdrop accidentally and inspect whether the dialog closes and what happens to the values.Repeat with a read-only information dialog. Ask the supplier to distinguish a harmless dismissal from leaving a task that contains meaningful unsaved work.If confirmation is provided, choose to keep editing and then deliberately discard. Both routes should return to a useful position and behave as described.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.