These two required calls (ZoomMtg.preLoadWasm and ZoomMtg.prepareJssdk) are mysterious in their side effects on the DOM and on the globally scoped CSS. I couldn’t find any information about this in the documentation and I couldn’t use the Devtools debugger to deduce it easily for myself. Including these calls (actually ZoomMtg.preLoadWasm by itself is enough) has some unexpected side-effects on my page layout though. Would it be possible for the Zoom dev team to disclose the “global” effects of these calls so that we can properly account for / cope with them in our web application?
Which Web Client SDK version?
Device (please complete the following information):
- Browser: Chrome
- Browser Version: 90.0.4430.93 (Official Build) (64-bit)
(Probably not relevant)