Skip to content

Conversation

@sethfowler-datadog
Copy link
Contributor

Motivation

The new encoding for DOM mutations being added in #4060 involves a new record type, BrowserChangeRecord. I've added support for BrowserChangeRecords to the replay sandbox. However, they don't yet work in the developer extension, because the replay sandbox version it's using is too old.

Changes

This PR updates the developer extension to use the latest version of the replay sandbox, bringing in support for playing back sessions that include BrowserChangeRecords.

Test instructions

  1. Check out this PR's branch.
  2. Build the extension locally and load it using Chrome's extension manager in the usual way.
  3. Go to staging. (It currently has the new serialization code; hopefully this doesn't get reset on Monday!)
  4. Use the developer extension to enable the use_change_records experimental feature.
  5. Confirm that Live Replay in the extension still works.

Checklist

  • Tested locally
  • Tested on staging
  • Added unit tests for this change.
  • Added e2e/integration tests for this change.

@sethfowler-datadog sethfowler-datadog requested a review from a team as a code owner January 9, 2026 17:49
Copy link
Contributor

@BeltranBulbarellaDD BeltranBulbarellaDD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, works as intended!

@sethfowler-datadog sethfowler-datadog merged commit 3548e9d into main Jan 12, 2026
22 checks passed
@sethfowler-datadog sethfowler-datadog deleted the seth.fowler/PANA-5359-support-change-records-in-developer-extension branch January 12, 2026 15:21
@github-actions github-actions bot locked and limited conversation to collaborators Jan 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants