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

Re: [webrtc-pc] RTCError extends DOMException (#2089)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 31 Jan 2019 13:24:07 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-459342366-1548941046-sysbot+gh@w3.org>
Reply to previously unaddressed comment:

> Section 11.1.2 says that sdpLineNumber is only set if the errorDetail value is "sdp-syntax-error". Would it make sense for sdpLineNumber to be set for other errorDetail values such as "hardware-encoder-not-available"/"hardware-encoder-error" (to indicate the specific encoder that is not available)?

Not sure, this is something that can happen at setParameters(), now when you're parsing SDP. I think having more info on that is a separate issue than this "refactoring" of RTCError.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2089#issuecomment-459342366 using your GitHub account
Received on Thursday, 31 January 2019 13:24:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:54 UTC