Monday, 29 February 2016
- I created PR 527, enabling trickling of end-of-candidates
- [webrtc-pc] Pull Request: Enable trickling of end-of-candidates through addIceCandidate.
- [webrtc-pc] NetworkError event is not defined and might not be needed
Friday, 26 February 2016
- [webrtc-pc] Pull Request: Add STUN Error Code reference
- [webrtc-pc] Pull Request: Add error codes reference
- [minutes] WebRTC Virtual Interim 25 Feb 2016
Thursday, 25 February 2016
- [webrtc-pc] Add API to control encrypted header extensions for RTP
- [webrtc-pc] Setting iceCandidatePoolSize to a non-zero value may initiate gathering
- [webrtc-pc] RTCPeerConnectionIceErrorEvent errorCode not defined
- Virtual Interim - Starts in 5 mins, join now.
- WebRTC Virtual Interim Meeting - Scribe?
- Closed: [webrtc-pc] Support for DTMF tones A-D
- [webrtc-pc] Merged Pull Request: Support for DTMF Tones
- [webrtc-pc] Merged Pull Request: Add activateReceiver method to RTCRtpTransceiver
- [webrtc-pc] Pull Request: Add text about 'remote sources' and how they are stopped (issue #513)
Wednesday, 24 February 2016
Tuesday, 23 February 2016
Monday, 22 February 2016
- [webrtc-pc] Clarify ICE consent freshness feedback
- [webrtc-pc] Pull Request: Support for DTMF Tones
- [webrtc-pc] Pull Request: Remove state check when ICE Agent is initialized (state is predictable)
- [webrtc-pc] Merged Pull Request: Use 'connection' as configuration target instead of User Agent (issue: #511)
Friday, 19 February 2016
Thursday, 18 February 2016
- How to signal loss of consent freshness
- [webrtc-pc] Merged Pull Request: Link cleanup (and typos)
- [webrtc-pc] Closed Pull Request: Fix typos relating to RTCRtpSender objects.
- [webrtc-pc] Pull Request: Link cleanup (and typos)
- Closed: [webrtc-pc] RID as read-only in setParameters()
- Closed: [webrtc-pc] can't use MUST on scaleResolutionDownBy input
- Closed: [webrtc-pc] Section 5.2.4: Definition of Active for an RTCRtpReceiver
- Closed: [webrtc-pc] Add activateSender() method
- Closed: [webrtc-pc] Creating an ICE agent is not defined
- [webrtc-pc] Merged Pull Request: Gather spec text about the ICE Agent at one place (also fixes: #331 and #332)
- [webrtc-pc] Merged Pull Request: RID unmodifiable in setParameters()
- [webrtc-pc] Merged Pull Request: Add getParameters() method to RTCRtpReceiver
- [webrtc-pc] Merged Pull Request: Fix "transeceivers" typos
- [webrtc-pc] Merged Pull Request: Reserve and use RangeError for scaleResolutionDownBy < 1.0.
- [webrtc-pc] Merged Pull Request: Definition of Active for an RTCRtpReceiver
- [webrtc-pc] Closed Pull Request: Make DataChannels Transferable and explain the implications
- [webrtc-pc] Closed Pull Request: Make RTCDataChannels Transferable
- [webrtc-pc] Handling the stopping of a track should be described
- [webrtc-pc] Pull Request: Use 'connection' as configuration target instead of User Agent (issue: #511)
- [webrtc-pc] The 'set a configuration' algorithm should modify a 'connection' rather than the User Agent
- [webrtc-pc] Pull Request: Gather spec text about the ICE Agent at one place (also fixes: #331)
- Re: maxHeight and maxWidth
- [webrtc-pc] Pull Request: RID unmodifiable in setParameters()
Wednesday, 17 February 2016
- [webrtc-pc] Pull Request: Fix typos relating to RTCRtpSender objects.
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- [webrtc-pc] Pull Request: Make the definition of addIceCandidate() more explicit (issue: #336)
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: Should we add a RIDs parameter to PeerConnection.addTrack?
- Re: Should we add a RIDs parameter to PeerConnection.addTrack?
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- RE: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- Should we add a RIDs parameter to PeerConnection.addTrack?
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Pull Request: Add activateReceiver method to RTCRtpTransceiver
- RE: maxHeight and maxWidth
Tuesday, 16 February 2016
- Re: maxHeight and maxWidth
- [webrtc-pc] Pull Request: Add getParameters() method to RTCRtpReceiver
- [webrtc-pc] Pull Request: Add getParameters() method to RTCRtpReceiver
- [webrtc-pc] Pull Request: Fix "transeceivers" typos
- Closed: [webrtc-pc] RID as read-only in setParameters()
- [webrtc-pc] Closed Pull Request: RID as read-only in setParameters()
Monday, 15 February 2016
- [webrtc-pc] Merged Pull Request: Fix a typo
- New webrtc-pc Editor's draft (v20160215)
- [webrtc-pc] Merged Pull Request: Fix to use correct character
- [webrtc-pc] Pull Request: Fix a typo
Sunday, 14 February 2016
- Re: Issue 497: RID as read-only in setParameters()?
- Re: Should we get drop RTCAnswerOptions?
- Re: Should we get drop RTCAnswerOptions?
- Re: Dropping SDP-specific errors
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- [webrtc-pc] Pull Request: Fix to use correct character
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
Saturday, 13 February 2016
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
Friday, 12 February 2016
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
- Re: maxHeight and maxWidth
Thursday, 11 February 2016
- Re: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- RE: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- RE: Issue 497: RID as read-only in setParameters()?
- Re: Issue 497: RID as read-only in setParameters()?
- [webrtc-pc] Pull Request: Reserve and use RangeError for scaleResolutionDownBy < 1.0.
- Section 5.2.4: Definition of Active for an RTCRtpReceiver
- Issue 497: RID as read-only in setParameters()?
- [webrtc-pc] Pull Request: Certificate API: add keygenAlgorithm attribute
- [webrtc-pc] Pull Request: RID as read-only
- Closed: [webrtc-pc] getSenders/getReceivers: optional kind parameter?
- [webrtc-pc] Closed Pull Request: getSenders/getReceivers: optional kind parameter
- [webrtc-pc] RID as read-only
- [webrtc-pc] Merged Pull Request: Change setParameters call to be Async
- Closed: [webrtc-pc] RTCRtpSender.get/setParameters is underspecified
Wednesday, 10 February 2016
- maxHeight and maxWidth
- [webrtc-pc] Merged Pull Request: Add PeerConnection.activateSender() and update early media example.
- [webrtc-pc] Certificate API: Do we need certificate introspection?
- [webrtc-pc] File a WebIDL issue to add the DOMException names WebRTC needs
Tuesday, 9 February 2016
Monday, 8 February 2016
Friday, 5 February 2016
Thursday, 4 February 2016
- Closed: [webrtc-pc] should "queue a task to fire a simple event"
- Closed: [webrtc-pc] Need to specify error when rejecting invalid SDP changes
- Closed: [webrtc-pc] impact of bundle and rtcp-mux on the number of Transports
- [webrtc-pc] Merged Pull Request: Need to specify error when rejecting invalid SDP changes
- Closed: [webrtc-pc] Work through error definitions
- [webrtc-pc] Merged Pull Request: Update error reports to align with existing DOM Errors
- [webrtc-pc] Pull Request: Need to specify error when rejecting invalid SDP changes
Wednesday, 3 February 2016
- Re: Dropping SDP-specific errors
- Re: Dropping SDP-specific errors
- Re: Dropping SDP-specific errors
- [webrtc-pc] Merged Pull Request: Replace DOMError with DOMException
- Closed: [webrtc-pc] DOMError is removed from the platform; use DOMException instead