- From: Justin Uberti via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Nov 2020 11:08:42 +0000
- To: public-webrtc-logs@w3.org
I could get behind a delineation where missing, unknown, or unparsable data results in an exception (i.e., the current behaviors defined in https://w3c.github.io/webrtc-pc/#set-the-configuration) and values that just exceed some protocol limit result in an async error, the same as if the server had enforced the check. -- GitHub Notification of comment by juberti Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/52#issuecomment-728857320 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:08:44 UTC