- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Nov 2020 00:49:33 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc: == Use relevant settings object instead of current settings object == [Today](https://w3c.github.io/webrtc-pc/#dfn-documentorigin): _"Let connection have a **[[DocumentOrigin]]** internal slot, initialized to the [current settings object](https://html.spec.whatwg.org/multipage/webappapis.html#current-settings-object)'s origin."_ This seems like an honest mistake since the origin associated with any DOM object by definition is in the _[relevant global object](https://html.spec.whatwg.org/multipage/webappapis.html#relevant-settings-object)_. Unlike https://github.com/w3c/mediacapture-main/issues/748 this seems largely editorial, since in both cases the origin would appear to be the same in all observable cases in practice. E.g. ```js await iframe.contentWindow.RTCPeerConnection.generateCertificate(keygen); // same-origin or SecurityError ``` Still, we should follow the [general advice](https://html.spec.whatwg.org/multipage/webappapis.html#concept-relevant-everything) to be consistent: > In general, web platform specifications should use the relevant concept, applied to the object being operated on (usually the this value of the current method). Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2604 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 November 2020 00:49:35 UTC