W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

[webrtc-pc] Maybe RTCError doesn't have to be named "RTCError" (#2330)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Oct 2019 23:55:06 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-508157969-1571270105-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc:

== Maybe RTCError doesn't have to be named "RTCError" ==
Since no browsers implement RTCError yet, concerns were raised about backwards 
compatibility with implementing it.

`RTCError` is both a *type* (with extra attributes), as well as the name of the error.

One idea to mitigate compat concerns would be to specify the error names browsers are using today. [E.g.](https://jsfiddle.net/jib1/r0vL78gw/):
await pc.setRemoteDescription({type: "offer", sdp: "foo"}); // OperationError
On the upside it solves compat. On the downside, JS that cares about the attributes would need to check for them.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2330 using your GitHub account
Received on Wednesday, 16 October 2019 23:55:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC