- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Jul 2018 21:55:04 +0000
- To: public-webrtc-logs@w3.org
> What wrong behavior would it lead to?
In the specific case of RTCPeerConnection, say you have code that does:
createOffer(someOptions, 5)
If you are only aware of the one-arg version of the function, you expect this to do the behavior corresponding to `someOptions`. With the three-arg overload in play, this will always return a rejected promise, because `5` cannot be coerced to `RTCPeerConnectionErrorCallback`.
--
GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1897#issuecomment-401949843 using your GitHub account
Received on Monday, 2 July 2018 21:55:11 UTC