- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Nov 2024 16:45:11 +0000
- To: public-webrtc-logs@w3.org
> I'd be more comfortable _allowing_ this behavior than _mandating_ it. I would go with mandating the behaviour, otherwise there is no real point for a spec. I think it is ok for spec to go first if we are confident implementations follow. > * 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. What are we trying to protect? Thinking about it more, given `groupId` is not a stable ID, I think it is fine to do the same for display tracks. > * 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. Device IDs should be hashed per origins yes, just like cameras and microphones. Or hashed per document, like `groupId`. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/308#issuecomment-2455202635 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 16:45:12 UTC