✨ [PANA-5359] - Support Change records in the developer extension #4072
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
The new encoding for DOM mutations being added in #4060 involves a new record type,
BrowserChangeRecord. I've added support forBrowserChangeRecords 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
use_change_recordsexperimental feature.Checklist