W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > September 2018

[mediacapture-output] Should setSinkId be functional in SecureContext only?

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 28 Sep 2018 17:49:34 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-364983133-1538156973-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-output:

== Should setSinkId be functional in SecureContext only? ==
Following on https://github.com/w3c/webrtc-pc/issues/1945, would it make sense to make *setSinkId* `[SecureContext]`? I.e.
console.log("setSinkId" in document.createElement('video')); // false in http
We're looking for guidance on implementing it in Firefox.

Currently, in Chrome this method exists in http, but is pretty much [useless](http://jsfiddle.net/jib1/Lumb0w6e/) (`SecurityError`).

As to the read-only`sinkId` attribute, we could leave it (`""`) or make it SecureContext as well (`undefined`). With no way to affect the attribute, it serves little purpose.

Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/78 using your GitHub account
Received on Friday, 28 September 2018 17:49:35 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:45 UTC