W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

Re: [webrtc-pc] Section 8.2: Null selector properly handled by getStats?

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Mon, 12 Jun 2017 19:10:46 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-307890217-1497294644-sysbot+gh@w3.org>
Mostly a style question how to resolve this. One way:
4. If selectorArg is null, let selector be null.
5. If selectorArg is a valid MediaStreamTrack let selector be a RTCRtpSender or RTCRtpReceiver on connection which track member matches selectorArg. If no such sender or receiver exists, or if more than one sender or receiver fit this criteria, return a promise rejected with a newly created InvalidAccessError.

Also I am not sure if the [definition of valid](http://w3c.github.io/webrtc-pc/#introduction-1) allows the InvalidAccessError to be thrown. Possibly "valid" in step 3 should be removed?

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1374#issuecomment-307890217 using your GitHub account
Received on Monday, 12 June 2017 19:10:53 UTC

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