- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 20:40:13 +0000
- To: public-webrtc-logs@w3.org
Firefox [uses](https://searchfox.org/mozilla-central/rev/734887cfb193b5697e59a857d394e8d4245996db/dom/media/MediaManager.cpp#3414) option 1 today but we'd love to get away from it if possible. I like the Safari behavior described above, but webcompat seems questionable since websites handle `ended` poorly. I simulated it in Firefox by removing `Allowed Temporarily ✕` in the URL bar's permission dropdown (which [won't block](https://jsfiddle.net/jib1/exvwLf8u/show)): Does website recover from cam+mic `ended`? | cam | mic -|-|- Meet (in room) | ✅ automatic | ❌ unrecoverable Zoom (in room) | ✅ after user toggle | ❌ unrecoverable Teams (in room) | ✅ after user toggle | ✅ after user toggle Cisco (in room) | ✅ after user toggle | ❌ unrecoverable Whereby (in room) | ❌ unrecoverable | ✅ automatic Jitsi (in room) | ❌ unrecoverable¹ | ❌ unrecoverable¹ Of course ↻ us a fine workaround, but some outreach would seem necessary to improve this. @youennf somewhat related, what does Safari do with BFCache of connected/unconnected RTCPeerConnections? --- <sub>1. Not counting users with 2+ devices able to recover by flipping device back and forth.</sub> -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/974#issuecomment-1906882243 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 20:40:16 UTC