Make browser Back behave predictably with large overlays

What to change

Agree a consistent browser-history behaviour for overlays that function like a separate navigation step.

A worked example

Illustrative example

A visitor opens a full-screen location chooser from a form and uses Back to return to that form with its entered details retained.

How to check the result

Accept when browser navigation follows the agreed mental model and does not unexpectedly discard work or create repeated empty history entries.

A mistake to avoid

Intercepting every Back action can be equally confusing if the visitor is deliberately trying to leave the website.

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 full-screen search or selection panel and press the browser Back button. Compare the result with the panel's visible close or return action.Repeat after selecting a result and after opening the panel from a deep page. Ask the supplier to show how history entries are handled.Use Forward after dismissal where relevant. The resulting state should be complete and understandable rather than a blank overlay or stale result set.

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.