This is more than urgent (just to make sure you understood the point).
If it’s not fixed before Chrome 100 is out there & use the major version, the web SDK won’t work anymore. Not only for us but also for people being in the same meetings than those joining via the Web SDK. (or Meeting & Video - if this code is shared / duplicated across sdks)
Can you please tell us when this fix can be released ?
Either on the 2.3.0 that is supposed to be released early March, or as a hotfix 2.2.1 if the 2.3.0 cannot be released for any reasons before Chrome 100 is (plannned on March 29)
Thank you for providing this additional context. I’ve shared these details and created another internal ticket to have this matter investigated. Here is the ticket number for your record [ZSEE-43399]. More to follow as updates become available.
We appreciate your feedback @lfrancia and @nvivot ! Please do let us know if you have anythings you might want to share --we’re here to listen!
Thank you for the additional details. As a follow-up, this issue [ZSEE-43399] has been marked as a bug, and our engineers are working on a fix. Another update will be provided when more details become available.
I heard that the 2.3.0 will include a fix for this bug, and should be released soon.
But we got no dates, and Chrome 100 will be official in 3 weeks. Would be great if you can release the 2.3.0 at least 2 weeks before Chrome 100 so that we have enough time to test it & do the upgrade before it’s too late and the damages are done.