BUG: Zoom Web Client does not enable audio or video on Breakout Room when the BO is being recorded

Description
We noticed that, when entering a BO that is being recorded, the Zoom Web client does not enable the audio and video buttons.

It seems it happens because inside the BOs the Zoom Web client does not show the consent message (“This meeting is being recorded. Do you want to come in or go out?”), and the buttons are enabled only after the user consents.

Browser Console Error
No console errors. The console messages are exactly the same as when entering a non-recording room.

Which Web Meeting SDK version?
It’s present in the most current Zoom Web client up to now.

To Reproduce(If applicable)

  1. zoom client: start new meeting
  2. zoom client: launch two breakout rooms, with manual (not automatic) user association
  3. zoom client: copy the meeting link
  4. zoom client: ingress the Breakout “Room 1”
  5. browser: paste the meeting link and go
  6. browser: don’t accept opening the meeting in the Zoom Client.
  7. browser: click the “join via browser” link
  8. browser: write your name and join the meeting
  9. zoom client: approve the participant in the meeting
  10. zoom client: start recording the Breakout Room 1
  11. zoom client: move the browser user to the Breakout Room 1
  12. browser: check that the consent popup has not been shown and the audio and vídeo buttons are disabled
  13. zoom client: move the browser user to the Breakout Room 2
  14. browser: check that the audio and vídeo buttons are enabled

Screenshots
Zoom Web - disabled audio and video buttons on BO being recorded

Troubleshooting Routes
Stop recording prior to the participant coming in - not acceptable for our business needs.

Device (please complete the following information):

  • Device: Dell Latitude 3400
  • OS: Windows 10 22H2
  • Browser: Chrome
  • Browser Version 108.0.5359.99

After opening this issue with Zoom Support they closed it saying it should be posted here.

Well, it’s posted here for 26 days with no replies…

Alberto, I was informed it has been fixed.
Can you confirm the bug has been solved?
Thanks