- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jul 2017 16:44:43 +0000
- To: public-webrtc-logs@w3.org
TL;DR: Have the conformance criteria thus far been basically "blanket implement all members"? If so, a blanket update of webrtc-pc to match webrtc-stats should suffice. Renaming is simple, but how to handle new fields? We probably should require them, unless there were fields explicitly left out last time the conformance criteria were updated. Anyone know? Thanks @soareschen for the list! Stats innovation generally happens in webrtc-stats, so webrtc-pc is lagging, and should be updated, in spite of the official conformance criteria pointing the other way. * RTCCodecStats - See https://github.com/w3c/webrtc-stats/pull/168 (which ironically came from webrtc-pc). * RTCRTPStreamStats - s/`associateStatsId`/`remoteId`/ + `localId`, s/`isRemote`//, s/`mediaTrackId`/`trackId`/ - from https://github.com/w3c/webrtc-stats/pull/191. * `roundtripTime` moved to [RTCRemoteInboundRTPStreamStats](https://w3c.github.io/webrtc-stats/#dom-rtcremoteinboundrtpstreamstats) - also https://github.com/w3c/webrtc-stats/pull/191. Those are the ones from your list I know off the top of my head. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1474#issuecomment-315407754 using your GitHub account
Received on Friday, 14 July 2017 16:44:50 UTC