Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add RTCPeerConnection constructor error to spec. #197

Merged
merged 3 commits into from
Nov 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -3918,6 +3918,24 @@ at the expense of some utility.
</wpt>
</div>

<h3 id=webrtc-monkeypatch>WebRTC</h3>

The [[WEBRTC]] specification defines "ECMAScript APIs in WebIDL to allow media and generic
application data to be sent to and received from another browser or device implementing the
appropriate set of real-time protocols." The interface which facilitates connections to peers is
{{RTCPeerConnection}}. Construction of this interface, and therefore connection to peers via
WebRTC, is disallowed in fenced frames.

<div algorithm=webrtc-constructor>
Modify the {{RTCPeerConnection}} {{RTCPeerConnection/constructor}} algorithm to add new first and
second steps that read:

1. Let |navigable| be [=this=]'s [=relevant global object=]'s [=Window/navigable=].
VergeA marked this conversation as resolved.
Show resolved Hide resolved

1. If |navigable|'s [=traversable navigable=] is a [=fenced navigable container/fenced
navigable=], throw a {{NotAllowedError}} {{DOMException}}.
VergeA marked this conversation as resolved.
Show resolved Hide resolved
</div>

<h2 id=security-and-privacy>Security & Privacy Considerations</h2>

This material is being upstreamed from our explainer into this specification, and in the meantime
Expand Down
Loading