Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support manual canvas snapshotting #108

Merged
merged 3 commits into from
Jul 28, 2023
Merged

Conversation

Vadman97
Copy link
Member

@Vadman97 Vadman97 commented Jul 27, 2023

@Vadman97 Vadman97 requested review from a team and et and removed request for a team July 27, 2023 21:33
@Vadman97 Vadman97 marked this pull request as ready for review July 27, 2023 21:33
@Vadman97 Vadman97 merged commit 7d8da02 into master Jul 28, 2023
Vadman97 added a commit to highlight/highlight that referenced this pull request Jul 28, 2023
## Summary

WebGL canvas elements can be double buffered, meaning that the canvas
bitmap is not in javascript memory
when we try to call `createImageBitmap`. If we hook into the webgl
render loop of a given library to do the
snapshotting, we have access to the canvas as it is still in memory.

Adds a new manual snapshotting mode that exposes this functionality.

Adds new rrweb logic in highlight/rrweb#108

## How did you test this change?

Babylon.js canvas snapshotting correctly in manual mode.
<img width="1234" alt="Screenshot 2023-07-27 at 2 33 46 PM"
src="https://github.com/highlight/highlight/assets/1351531/5e06a582-ebf1-45e3-af9b-2360e028cb58">

New docs on [vercel
preview](https://highlight-landing-ld05dz2bn-highlight-run.vercel.app/docs/getting-started/client-sdk/replay-configuration/canvas).

## Are there any deployment considerations?

New highlight.run minor version.
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