---
title: "Restore filtered list context with browser Back"
description: "Verify returning from a record detail restores the previous query, filter, page, and selected record position according to the product navigation contract."
canonical_url: "https://vostride.com/agent-library/navigation-routing/back-restores-list-context.md"
md_url: "https://vostride.com/agent-library/navigation-routing/back-restores-list-context.md"
content_kind: "recipe"
topic: "navigation-routing"
---

# Restore filtered list context with browser Back

Verify returning from a record detail restores the previous query, filter, page, and selected record position according to the product navigation contract.

## Risk

Back navigation can reconstruct a default list and discard the context that led to the record. Choose independent fixtures for membership and pagination so restoration is more than a matching page heading.

## Fixtures

- A test issue list contains twelve Open release issues plus closed and unrelated controls.
- The active list state is query release, status Open, page two at a configured page size of five.
- The contract preserves query, filters, and page through detail navigation and browser Back.

## Steps

1. Open the list, apply the prepared query and status filter, and navigate to page two.
2. Verify the expected page-two keys, then open its second fixture issue and verify the detail key.
3. Use browser Back and verify the query still reads release, Open remains applied, and page two is selected.
4. Verify the same five expected page-two identifiers are visible and the opened issue is among them.
5. Use browser Forward to return to the detail and verify its original issue key, then Back again to confirm repeatable restoration.

## Expected results

- The restored controls represent the complete previous list state.
- The visible result membership and page boundary match the independent prepared set.
- Forward returns to the same detail identifier rather than a newly selected row from the rebuilt list.

## False-pass traps

- A list title matching Issues says nothing about query or page preservation.
- Using the app breadcrumb instead of browser Back may follow a different navigation contract.

## Cleanup

- Remove fixture issues and clear saved list context for the QA account.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Navigation and routing QA recipes](/agent-library/navigation-routing.md)
- [Software factory QA library](/agent-library.md)