- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Nov 2020 11:17:17 +0000
- To: public-webrtc-logs@w3.org
That sounds reasonable to me, for what it's worth. (Fetch and XMLHttpRequest will also throw exceptions on the API side for similar reasons.) The main thing in my mind is to centralize on a "network error" for what might change over time and is not really the concern of the API itself, such as ports, mixed content blocking, CSP, etc. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/52#issuecomment-728861480 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 November 2020 11:17:22 UTC