- From: Kevin Gibbons via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Feb 2019 16:03:32 +0000
- To: public-webrtc-logs@w3.org
That's up to the Chrome team, presumably. I think there's very little chance anyone is depending on the current behavior yet, since manually constructing RTCError is a pretty weird thing to do and since 73 is not yet stable, so I would be very surprised if this change broke anyone right now. For what it's worth, I'd never have noticed this if Chrome hadn't shipped it to the unstable channels. It seems a shame to say that API decisions like this are set in stone at exactly the point at which users can start experimenting with them and giving feedback. -- GitHub Notification of comment by bakkot Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2111#issuecomment-468329332 using your GitHub account
Received on Thursday, 28 February 2019 16:03:33 UTC