- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Apr 2021 20:40:29 +0000
- To: public-webrtc-logs@w3.org
> Having origin+application-specific string is ok in the sense that there is a trusted scope and the application-specific string wocanld be evaluated based on that trusted scope. Origin leakage would be opt-in based on setting the application-specific string. (1) `Origin` + (2) `application-specific string` would be perfect for us; even better for analytics than what I had originally suggested. If we have agreement in principle (do we?), we could move on to discuss specifics. Collating your messages, I think this proposal would be acceptable to us both: Define `MediaDevices.captureHandle`, settable by an application. If set, the application consents to exposing the origin as `MediaTrackSettings.displayName` and the `captureHandle` itself as `MediaTrackSettings.displaySource` by potential capturing applications. (Only the top-level document's value is of consequence.) Wdyt? (Some minor details left for later discussion, such as setting back to `undefined`/`empty-string`. I don't foresee major disagreements there.) -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/159#issuecomment-815247663 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 April 2021 20:40:31 UTC