Skip to content

Conversation

@eoghanmurray
Copy link
Contributor

Discovered that the common case of mouse movement or scrolling happening during takeFullSnapshot was causing mutations to be immediately emitted, contrary to the goal of #385

Instead create two different types of 'lock' for mutations, one to do with freezes initiated by inactivity (which can be unlocked by any new non-mutation activity) and another lock during fullSnapshot, which can't be unlocked until the fullSnapshot is finished.

…ing during `takeFullSnapshot` was causing mutations to be immediately emitted, contrary to the goal of rrweb-io#385
@Yuyz0112
Copy link
Member

Thanks

@Yuyz0112 Yuyz0112 merged commit 9187bec into rrweb-io:master Jan 31, 2021
eoghanmurray added a commit to statcounter/rrweb that referenced this pull request Feb 3, 2021
…ing during `takeFullSnapshot` was causing mutations to be immediately emitted, contrary to the goal of rrweb-io#385 (rrweb-io#470)
eoghanmurray added a commit to statcounter/rrweb that referenced this pull request Feb 22, 2021
…ing during `takeFullSnapshot` was causing mutations to be immediately emitted, contrary to the goal of rrweb-io#385 (rrweb-io#470)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants