Establish what is happening
Capture the starting state
Record query, selected facets, sort, page, view, and any category context before navigating. Save the URL and visible controls. Include a narrow-screen path if its navigation differs, but keep the same search state for comparison.
Trace each transition
Move through pagination, sorting, result detail, browser back, and a copied link. Compare URL, history, form values, result set, and scroll position where relevant. Mark the first transition that drops or mutates a selection.
Name persistence rules
List fields that must survive, fields that should reset, and fields with a deliberate context change. Preserve a failing URL and a successful control. Do not describe every state as lost when only page or scroll is meant to change.
What to carry forward
The triage output is a state contract with a failing transition, preserved URL, and intentional reset rules. Stop when another reviewer can replay the loss. If the product has not decided a field’s lifetime, route that design question before implementing navigation changes.
Technical background: Adobe developer documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow