Replay Details: playback restarts from 0:00 when selecting a Network request or switching Request/Response tabs

[InterstellarStella]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Open a web (rrweb) replay on the Replay Details page and start playback.
2. Let it play for a while, then open the Network tab.
3. Select any network request, or switch between the Request and Response tabs of a selected request.

Reproduced on a customer's replay by the customer and by Sentry Support, on the same replay. It does not reproduce consistently in other orgs.

Expected Result

Playback keeps its current position while inspecting network request details.

Actual Result

Playback jumps back to 0:00, so the user loses their place and has to seek again. This makes debugging requests in a replay difficult.

Observed in DevTools at the moment of the restart:

• A POST to /api/0/projects/<org>/<project>/replays/<replay_id>/viewed-by/ fires.
• No other replay requests fire. No refetch of the replay record (/organizations/<org>/replays/<replay_id>/) and no recording-segments requests.

Product Area

Replays

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[linear-code]

ENG-8687

[getsantry]

Routing to @getsentry/product-owners-replays for triage ⏲️

[JoshuaKGoldberg]

Confirmed, I can reproduce the bug. It looks to me that the player is still being torn down and rebuilt whenever any replay data changes (something we'd tried to fix previously). Looks like we missed a spot. Thanks for the bug report! I'll work on fixing this.