[Webkit-unassigned] [Bug 259488] New: Cannot use camera/microphone device in multiple windows/tabs simultaneously

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=259488

            Bug ID: 259488
           Summary: Cannot use camera/microphone device in multiple
                    windows/tabs simultaneously
           Product: WebKit
           Version: Safari 16
          Hardware: Mac (Apple Silicon)
                OS: macOS 13
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: btham at cisco.com
                CC: youennf at gmail.com

I'm working on test automation for our web app, which does a WebRTC call between two windows/tabs. For example, a simple test might involve one Safari window/tab starting a WebRTC call with a microphone/camera, another window/tab joining the call with a microphone/camera, and checking that audio and video are being sent and received. For test purposes, we are using the mock capture devices setting in Safari, but this issue also affects real capture devices.

When the second Safari window/tab starts their microphone/camera, the microphone from the first window/tab stops sending audio, and the camera from the first window/tab becomes black. My guess is that this is some privacy/security mechanism kicking in, but it does make it impossible to test WebRTC calls between 2 Safari windows/tabs.

This can be reproduced with this simple WebRTC sample: https://webrtc.github.io/samples/src/content/devices/input-output/. Simply open this link in 2 separate Safari windows/tabs.

This used to not be an issue as long as I opened them in separate windows (opening them in separate tabs, as far as I know, has always exhibited this behavior). This was about a year ago (sorry, I don't have the specific Safari version for you, but I assume it was macOS 12 and Safari 15). Now both opening in separate windows and opening in separate tabs exhibits this behavior. So I'm unsure if this is a regression; I couldn't find anything in the Safari patch notes about it.

If this is expected behavior, are there any ways to get around this limitation?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230725/22a63ad2/attachment.htm>