Skip to content

[Feature]: Trace Viewer UX Improvement - preserve and restore scroll position when returning to Actions List via "Show all" #40808

Description

@toduyemi

🚀 Feature Request

When debugging complex, long-running test flows in the Playwright Trace Viewer, I frequently need to investigate network activity and console logs tied to specific actions. The workflow usually involves:

  1. Scrolling deep into the long list of actions to find the area of interest.
  2. Double-clicking a specific action to filter down the network requests or console logs to just that step.
  3. Returning to the list, with "Show All" and clicking into the action above or below this. Rinse and repeat several times

The Problem:
The moment "Show all" is clicked, the action list's scroll state completely resets, throwing me back to the very top of the list (Step 1) rather than being able to bounce between Steps 2 and 3.

Because investigation usually requires jumping back and forth between a cluster of closely related actions located deep in the test execution, this reset forces me to constantly scroll all the way back down and visually re-locate my place. In tests with dozens or hundreds of steps, this creates massive scroll fatigue and breaks rhythm. Having to do this several times in as many minutes is painful.

Solution/Request
When a user clicks the "Show all" button to clear an active filter, the Trace Viewer should remember and return to the previous scroll position of the action list. Ideally, the action that was just being inspected should remain highlighted and kept perfectly in view, allowing for a seamless, iterative back-and-forth debugging experience. Essen

Motivation

This behaviour transforms what should be a quick, agile inspection of adjacent actions into an agonizing and repetitive navigation penalty on large test suites. Preserving the UI state here would big improve the dev experience during deep-dive RCA.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions