Yes that sounds like a good idea to me. Other uses of "trackId" that should move to the obsolete section: RTCInboundRtpStreamStats.trackId, RTCOutboundRtpStreamStats.trackId. If we still want to expose stream identifiers that more properly belongs to the sender and receiver state as a sequence<DOMString> streamIdentifiers. The webrtc-pc spec has shied away from streams for a while now so these might not be very interesting but that would be the right way to do it. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/361#issuecomment-419137097 using your GitHub accountReceived on Thursday, 6 September 2018 15:26:59 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:45 UTC