Wednesday, 28 February 2018
- [webrtc-stats] Pull Request: Add build status icon and README minor reflresh
- Re: Updated proposed charter
Tuesday, 27 February 2018
- Weekly github digest (WebRTC WG specifications)
- Result of the first webrtc developers survey
- Call for Consensus (CfC) to transition “WebRTC Statistics” to Candidate Recommendation” - respond by March 10, 2018
Monday, 26 February 2018
Saturday, 24 February 2018
Friday, 23 February 2018
- [webrtc-pc] Pull Request: Update mandatory to implement stats based on stats dictionary renames
- [webrtc-pc] Duplicate definitions errors (following udpate to respec 19.6.0)
- [webrtc-stats] WebIDL issue
- [webrtc-pc] Pull Request: Update webrtc-respec-ci integration following respec and Travis CI current practices
- [webrtc-stats] Normalize RTCPeerConnection and PeerConnection
Thursday, 22 February 2018
- [webrtc-pc] Pull Request: Create a Dtmf internal slot and initialize it in RtpSender
- [webrtc-stats] Pull Request: Update webrtc-respec-ci integration following respec current practices
- Plan for charter
- [minutes] WebRTC WG Virtual Interim 21 February 2018
Wednesday, 21 February 2018
- Re: Summary of "What would you like to see in WebRTC next?"
- [webrtc-pc] Recycling an m= section may not remove the old transceiver's remote track from its stream
- Re: Summary of "What would you like to see in WebRTC next?"
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-stats] Pull Request: obsolete RTCIceCandidatePairStats priority
- [webrtc-stats] Pull Request: renaming RTCRTPStreamStats to RTCRtpStreamStats
- [webrtc-stats] Pull Request: Renaming RTCRTPStreamStats to RTCRtpStreamStats
- [webrtc-stats] Pull Request: Add hugeFramesSent to RTCVideoSenderStats
- Summary of "What would you like to see in WebRTC next?"
- Re: What would you like to see in WebRTC next? A low-level API?
Tuesday, 20 February 2018
- Weekly github digest (WebRTC WG specifications)
- Re: Updated proposed charter
- [webrtc-pc] DTMF sending: Permit only in connected status?
- [webrtc-pc] Does RTCRtpSender's dtmf attribute return the same object every time?
Monday, 19 February 2018
- Re: Updated proposed charter
- [webrtc-pc] RTCPeerConnection lacks identity marker beyond current process
- Re: Updated proposed charter
- Reminder: VI Wednesday this week
- [webrtc-pc] DTMF should not send before connecting
Friday, 16 February 2018
Thursday, 15 February 2018
- New Editor for Screen Capture
- [webrtc-pc] Simplify candidate interaction by allowing Null
- [webrtc-stats] "make travissetup" does not work on mac
- Updated proposed charter
- [webrtc-pc] Pull Request: Enqueue replaceTrack, and remove sync setting of track.
Wednesday, 14 February 2018
- [webrtc-pc] Update mandatory to implement stats based on stats dictionary renames
- [webrtc-stats] Is isRemote on RTCIceCandidateStats still necessary?
Tuesday, 13 February 2018
- Weekly github digest (WebRTC WG specifications)
- [webrtc-pc] Pull Request: Evalution of direction not relevant for replaceTrack.
Monday, 12 February 2018
Saturday, 10 February 2018
Friday, 9 February 2018
Thursday, 8 February 2018
Wednesday, 7 February 2018
- [webrtc-pc] Pull Request: Fix remaining compat issue with respec 19
- [webrtc-stats] Pull Request: Rename "mediaType" to "kind" in RTCRTPStreamStats.
- [webrtc-stats] Pull Request: Moved trackId from RTCRTPStreamStats to RTC[In/Out]boundRTPStreamStats.
- [webrtc-stats] Track ID doesn't make sense for remote RTCRtpMediaStream stats
- [webrtc-stats] Clarify stats hierarchies
- [webrtc-stats] Pull Request: senderId and receiverId added to RTCRTPStreamStats
- [webrtc-stats] Pull Request: Rename sender/receiver/track dictionaries
- [webrtc-pc] Pull Request: RTCRtpTransceiver.direction is writable.
Tuesday, 6 February 2018
- Weekly github digest (WebRTC WG specifications)
- [webrtc-pc] Transceiver kind attribute
- Re: WPT test dependencies
- Re: WPT test dependencies
Monday, 5 February 2018
- [webrtc-pc] reducing audio packet rate while track is disabled
- Re: WPT test dependencies
- [webrtc-stats] RTCIceCandidatePairStats.priority is wrong
- [webrtc-pc] Pull Request: Fix compatibility with ReSpec 19
- Re: How to register with Google as a WebRTC developer
- How to register with Google as a WebRTC developer
- Re: What would you like to see in WebRTC next? A low-level API?
Friday, 2 February 2018
- [webrtc-pc] Pull Request: Removing 'readonly' from Tranceiver's 'direction'.
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-pc] Initial data channel state is inconsistent
- [webrtc-pc] RTCRtpSynchronizationSource.audioLevel algorithmic equality
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
Thursday, 1 February 2018
- [webrtc-pc] Pull Request: Change [[AssociatedMediaStreams]] to [[AssociatedMediaStreamIds]]
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-pc] pc.addTrack/removeTrack are confusing and mostly redundant. Mark as legacy?
- [webrtc-pc] Respec errors uncovered by Respec-19
- [webrtc-stats] Pull Request: Define timestamps as performance.timeOrigin + performance.now()
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-pc] need to clear [[AssociatedMediaStreams]] in removeTrack?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?