# Are there any known issues with using multiple canvas elements for peer video streams?

**URL:** <https://devforum.zoom.us/t/are-there-any-known-issues-with-using-multiple-canvas-elements-for-peer-video-streams/55948>\
**Category:** Web\
**Created:** [August 17, 2021, 4:06pm UTC](https://devforum.zoom.us/t/are-there-any-known-issues-with-using-multiple-canvas-elements-for-peer-video-streams/55948 "2021-08-17T16:06:55Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [September 1, 2021, 1:22am UTC](https://devforum.zoom.us/t/are-there-any-known-issues-with-using-multiple-canvas-elements-for-peer-video-streams/55948/9 "2021-09-01T01:22:56Z")

</div>

Hey @tommy @vitalyateventcadence

In react sample app, wepack devserver returns the correct CORP headers, but in purejs demo, it doesn’t. Rendering multiple videos requires [SharedArrayBuffer](https://marketplace.zoom.us/docs/sdk/native-sdks/web/advanced/web-isolation).

Thanks  
Vic

---

_[View the full topic](https://devforum.zoom.us/t/are-there-any-known-issues-with-using-multiple-canvas-elements-for-peer-video-streams/55948)._
