- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Nov 2024 10:40:03 +0000
- To: public-webrtc-logs@w3.org
On the one hand, yes, this seems potentially useful. On the other hand, realistically, we cannot expect all user agents to prioritize this work in the short-term. I'd be more comfortable _allowing_ this behavior than _mandating_ it. I'd also suggest scoping the persistence of the ID to successive getDisplayMedia() calls by the same Document. That is: - If the user reloads the the video conferencing application, the capturing app should get new IDs. Otherwise, we'd be exposing which tabs/windows are still there, which needlessly goes beyond the current MVP. - If the user has `tab1` dialed to `origin1` and `tab2` dialed to `origin2`, and both embed `vc-in-iframe.com` that calls gDM, then we should expose separate yet persistent IDs for similar reasons. Wdyt? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/308#issuecomment-2454365392 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 November 2024 10:40:04 UTC