- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Aug 2020 11:02:55 +0000
- To: public-webrtc-logs@w3.org
> BTW another way to accomplish the same would be for the application itself to scan the remote SDP for unwanted media types and bail.
Yes, the polyfill I had simply overwrote SRD and then did those manipulations.
What we've been telling people for years is [this](https://w3c.github.io/webrtc-pc/#example-9):
```
signaling.onmessage = async ({data: {description, candidate}}) => {
try {
if (description) {
await pc.setRemoteDescription(description);
```
and JSEP [is saying](http://rtcweb-wg.github.io/jsep/#rfc.section.3.3)
```
most applications should be able to treat the SessionDescriptions produced and consumed by these various API
calls as opaque blobs; that is, the application will not need to read or change them
```
--
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2561#issuecomment-670462001 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 August 2020 11:02:57 UTC