public-webrtc-logs@w3.org from January 2019 by author

Alexander via GitHub

• Re: [mediacapture-image] Implementation status using torch on chrome under Windows 10 (#202) (Tuesday, 15 January)

Amit Hilbuch via GitHub

• [webrtc-pc] Pull Request: Clarifying how the simulcast envelope is created. (Tuesday, 22 January)
• Re: [webrtc-pc] Not clear how to set # of layers when answering an offer with a track (#2014) (Wednesday, 16 January)
• [webrtc-pc] Simulcast alternative layers do not have an API surface. (#2061) (Wednesday, 16 January)
• Re: [webrtc-pc] Do simulcast offers need to contain RIDs of all streams in both directions? (#2053) (Tuesday, 15 January)
• [webrtc-pc] Mismatch between RID restrictions and RTPEncodingParameters (#2054) (Saturday, 12 January)
• [webrtc-pc] Do simulcast offers need to contain RIDs of all streams in both directions? (#2053) (Saturday, 12 January)
• Re: [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described (#1896) (Saturday, 12 January)
• Re: [webrtc-pc] Valid RID values mismatch between specs (#2013) (Saturday, 12 January)

Anders Pitman via GitHub

• Re: [webrtc-pc] Obtain user consent for one-way media and data use cases (#2012) (Saturday, 5 January)

Andreas Pehrson via GitHub

• Re: [mediacapture-record] Recording a stream while adding/removing a track is not well defined (#151) (Friday, 25 January)
• Re: [mediacapture-record] Recording a stream while adding/removing a track is not well defined (#151) (Wednesday, 23 January)

armax00

• [mediacapture-main] Pull Request: Add clarification for overconstrained constraints evaluation. (Tuesday, 15 January)
• [mediacapture-main] Pull Request: Add clarification for overconstrained constraints evaluation. (Tuesday, 15 January)

benag via GitHub

• Re: [mediacapture-image] Implementation status using torch on chrome under Windows 10 (#202) (Tuesday, 15 January)
• [mediacapture-image] Implementation status using torch on chrome under Windows 10 (#202) (Tuesday, 15 January)

Bernard Aboba via GitHub

• [webrtc-pc] new commits pushed by aboba (Thursday, 31 January)
• Closed: [webrtc-pc] Make RTCError inherit from DOMException? (#2082) (Thursday, 31 January)
• [webrtc-pc] new commits pushed by aboba (Thursday, 31 January)
• Closed: [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described (#1896) (Thursday, 31 January)
• Re: [webrtc-pc] Don't require RTCRtpContributingSource.audioLevel to be present in some cases (#2046) (Thursday, 31 January)
• Closed: [webrtc-pc] Valid RID values mismatch between specs (#2013) (Tuesday, 29 January)
• Re: [webrtc-pc] Effect of RTCRtpSendParameters on Simulcast (#2085) (Tuesday, 29 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• Re: [webrtc-pc] RTCError extends DOMException (#2084) (Tuesday, 29 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• [webrtc-pc] new commits pushed by aboba (Friday, 25 January)
• [webrtc-pc] new commits pushed by aboba (Friday, 25 January)
• [webrtc-pc] new commits pushed by aboba (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Closed: [mediacapture-screen-share] respec warnings (#98) (Friday, 25 January)
• [mediacapture-screen-share] respec warnings (#98) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• [mediacapture-screen-share] Pull Request: Attempted fix for boolean errors (Thursday, 24 January)
• [webrtc-pc] Pull Request: Effect of RTCRtpSendParameters on Simulcast (Thursday, 24 January)
• [webrtc-pc] new commits pushed by aboba (Thursday, 24 January)
• Closed: [webrtc-pc] setCodecPreferences and RTX / RED / FEC codecs (#2028) (Thursday, 24 January)
• Closed: [webrtc-pc] Simulcast alternative layers do not have an API surface. (#2061) (Thursday, 24 January)
• Closed: [webrtc-pc] Mismatch between RID restrictions and RTPEncodingParameters (#2054) (Thursday, 24 January)
• Closed: [webrtc-pc] Do simulcast offers need to contain RIDs of all streams in both directions? (#2053) (Thursday, 24 January)
• [webrtc-pc] new commits pushed by aboba (Thursday, 24 January)
• [webrtc-pc] new commits pushed by aboba (Thursday, 24 January)
• Closed: [webrtc-pc] Clarify how codecs should be prioritized. (#2009) (Thursday, 24 January)
• [webrtc-pc] new commits pushed by aboba (Thursday, 24 January)
• [webrtc-pc] new commits pushed by aboba (Thursday, 24 January)
• Re: [webrtc-pc] setCodecPreferences and RTX / RED / FEC codecs (#2028) (Tuesday, 22 January)
• Re: [webrtc-pc] Mismatch between RID restrictions and RTPEncodingParameters (#2054) (Tuesday, 22 January)
• Re: [webrtc-pc] Do simulcast offers need to contain RIDs of all streams in both directions? (#2053) (Tuesday, 22 January)
• Re: [webrtc-pc] Simulcast alternative layers do not have an API surface. (#2061) (Tuesday, 22 January)
• [webrtc-pc] new commits pushed by aboba (Tuesday, 22 January)
• Closed: [webrtc-pc] Typo in setCodecPreferences() (#2076) (Tuesday, 22 January)
• [webrtc-pc] Pull Request: Simulcast SDP clarifications (Monday, 21 January)
• [webrtc-pc] Pull Request: Simulcast SDP clarifications (Monday, 21 January)
• [webrtc-pc] new commits pushed by aboba (Monday, 21 January)
• [webrtc-pc] new commits pushed by aboba (Monday, 21 January)
• Re: [webrtc-pc] Clarify how codecs should be prioritized. (#2009) (Monday, 21 January)
• [webrtc-pc] Pull Request: Effect of RTCRtpSendParameters on Simulcast (Monday, 21 January)
• [webrtc-pc] new commits pushed by aboba (Monday, 21 January)
• Re: [webrtc-pc] "Create an RTP sender" doesn't handle creating from SDP (#2072) (Monday, 21 January)
• [webrtc-pc] Pull Request: setCodecPreferences and RTX / RED / FEC codecs (Saturday, 19 January)
• [webrtc-pc] Pull Request: Reference draft-ietf-mmusic-rid Section 10 (Friday, 18 January)
• [webrtc-pc] new commits pushed by aboba (Friday, 18 January)
• [webrtc-pc] new commits pushed by aboba (Friday, 18 January)
• [webrtc-pc] Pull Request: Reference draft-ietf-mmusic-rid Section 10 (Friday, 18 January)
• Re: [webrtc-pc] Not clear how to set # of layers when answering an offer with a track (#2014) (Wednesday, 16 January)
• Re: [webrtc-pc] rtcpTransport should be null when bundling (#2057) (Tuesday, 15 January)
• Re: [webrtc-pc] Do simulcast offers need to contain RIDs of all streams in both directions? (#2053) (Monday, 14 January)
• Re: [webrtc-pc] Mismatch between RID restrictions and RTPEncodingParameters (#2054) (Monday, 14 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• Re: [webrtc-pc] Mismatch between RID restrictions and RTPEncodingParameters (#2054) (Monday, 14 January)

Domenic Denicola via GitHub

• Re: [webrtc-pc] It is not clear that RTCErrorDetailType is referencing things defined in another repo (#2083) (Thursday, 31 January)

Dominique Hazael-Massieux via GitHub

• [mediacapture-screen-share] Pull Request: Add missing references for external definitions (Friday, 25 January)
• Closed: [webrtc-pc] Add amithilbuch to assignable people (#2065) (Friday, 18 January)
• Re: [webrtc-pc] Add amithilbuch to assignable people (#2065) (Friday, 18 January)
• Re: [webrtc-pc] Add amithilbuch to assignable people (#2065) (Thursday, 17 January)

Florent Castelli via GitHub

• Re: [webrtc-pc] RTCRtpReceiver.getParameters() clarification (#2032) (Tuesday, 22 January)
• Re: [webrtc-pc] Need to define what to do on very low bitrates (#2003) (Thursday, 17 January)

François Daoust via GitHub

• Re: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Saturday, 19 January)
• Re: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Thursday, 17 January)
• Re: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Thursday, 17 January)

Harald Alvestrand via GitHub

• [mediacapture-main] new commits pushed by alvestrand (Thursday, 31 January)
• [mediacapture-main] new commits pushed by alvestrand (Thursday, 31 January)
• Closed: [mediacapture-main] Should getUserMedia promise be resolved only on pages that have focus (#560) (Thursday, 31 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• [webrtc-pc] new commits pushed by alvestrand (Thursday, 31 January)
• Re: [webrtc-pc] Clarifying how the simulcast envelope is created. (#2081) (Thursday, 31 January)
• Re: [webrtc-pc] Describe how RIDs are added to a media section (#2071) (Thursday, 31 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Thursday, 31 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• [webrtc-pc] Pull Request: Indicate where idp- errors are used. (Thursday, 31 January)
• Re: [webrtc-pc] It is not clear that RTCErrorDetailType is referencing things defined in another repo (#2083) (Thursday, 31 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 31 January)
• Re: [mediacapture-main] enumerateDevices is exposing devices labels for origins that are granted access once (#563) (Thursday, 31 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 31 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• Re: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Wednesday, 30 January)
• Re: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Wednesday, 30 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Saturday, 26 January)
• Re: [webrtc-pc] It is not clear that RTCErrorDetailType is referencing things defined in another repo (#2083) (Wednesday, 23 January)
• Re: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Wednesday, 23 January)
• Re: [webrtc-stats] add stunserverconnectionstats (#372) (Wednesday, 23 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Wednesday, 23 January)
• [webrtc-pc] Make RTCError inherit from DOMException? (#2082) (Wednesday, 23 January)
• Re: [webrtc-pc] Simulcast: Which layer gets dropped first? (#2080) (Tuesday, 22 January)
• Re: [webrtc-pc] Describe how RIDs are added to a media section (#2071) (Tuesday, 22 January)
• [webrtc-pc] Simulcast: Which layer gets dropped first? (#2080) (Tuesday, 22 January)
• [webrtc-pc] "Create an RTP sender" doesn't handle creating from SDP (#2072) (Monday, 21 January)
• [webrtc-pc] Pull Request: Describe how RIDs are added to a media section (Monday, 21 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Thursday, 17 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Thursday, 17 January)
• Re: [mediacapture-screen-share] Address corner-cases where getDisplayMedia() shows prompt only to fail afterwards. (#96) (Thursday, 17 January)
• Re: [mediacapture-main] Add clarification for overconstrained constraints evaluation. (#558) (Thursday, 17 January)
• Re: [webrtc-pc] Obtain user consent for one-way media and data use cases (#2012) (Thursday, 17 January)
• [webrtc-pc] Add amithilbuch to assignable people (#2065) (Thursday, 17 January)
• [webrtc-pc] new commits pushed by alvestrand (Thursday, 17 January)
• Closed: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Thursday, 17 January)
• Closed: [webrtc-pc] rtcpTransport should be null when multiplexing RTCP (#2057) (Thursday, 17 January)
• [webrtc-pc] new commits pushed by alvestrand (Thursday, 17 January)
• [webrtc-pc] Pull Request: Add description of DTLS transport error handling. (Thursday, 17 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Thursday, 17 January)
• [webrtc-pc] Pull Request: Mark dtlstransport's ICETransport attribue [SameObject] (Thursday, 17 January)
• [webrtc-pc] Pull Request: Mark dtlstransport's ICETransport attribue [SameObject] (Thursday, 17 January)
• Re: [webrtc-pc] Set rtcpTransport to null when multiplexing. (#2058) (Wednesday, 16 January)
• [webrtc-pc] Pull Request: Set rtcpTransport to null when multiplexing. (Wednesday, 16 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Wednesday, 16 January)
• Closed: [mediacapture-image] Implementation status using torch on chrome under Windows 10 (#202) (Tuesday, 15 January)
• Re: [mediacapture-image] Implementation status using torch on chrome under Windows 10 (#202) (Tuesday, 15 January)
• Closed: [webrtc-pc] setParameters: check for number of encodings (#2016) (Tuesday, 15 January)
• Re: [webrtc-pc] setParameters: check for number of encodings (#2016) (Tuesday, 15 January)
• [webrtc-pc] rtcpTransport should be null when bundling (#2057) (Tuesday, 15 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• Re: [webrtc-pc] Send transferable data (#2055) (Sunday, 13 January)
• Re: [webrtc-pc] Mismatch between RID restrictions and RTPEncodingParameters (#2054) (Sunday, 13 January)
• Closed: [webrtc-pc] RTCPriorityType is not documented for simulcast (#1888) (Thursday, 10 January)
• Re: [webrtc-pc] RTCPriorityType is not documented for simulcast (#1888) (Thursday, 10 January)
• Re: [webrtc-pc] Stop bundled transceivers when the offerer tagged is stopped. (#2050) (Thursday, 10 January)
• Re: [webrtc-pc] Define which m= section is offerer tagged. (#2048) (Thursday, 10 January)

henbos via GitHub

• Re: [mediacapture-screen-share] Define ownAudioCancellation (#94) (Thursday, 31 January)
• [webrtc-pc] Remove stopped transceivers from getTransceivers() (#2092) (Thursday, 31 January)
• [webrtc-pc] Update WebIDL reference in Terminology (#2091) (Thursday, 31 January)
• Re: [mediacapture-screen-share] Define ownAudioCancellation (#94) (Thursday, 31 January)
• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Thursday, 31 January)
• Re: [webrtc-pc] RTCError extends DOMException (#2089) (Thursday, 31 January)
• Re: [webrtc-pc] RTCError extends DOMException (#2084) (Thursday, 31 January)
• Re: [webrtc-pc] RTCError extends DOMException (#2089) (Thursday, 31 January)
• [webrtc-pc] Pull Request: RTCError extends DOMException (Thursday, 31 January)
• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Wednesday, 30 January)
• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Wednesday, 30 January)
• [mediacapture-screen-share] Audio is said to be optional but there's one place that implies that it is not (#101) (Wednesday, 30 January)
• Closed: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Wednesday, 30 January)
• Re: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Wednesday, 30 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Wednesday, 30 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Tuesday, 29 January)
• Re: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Tuesday, 29 January)
• Re: [webrtc-pc] RTCError extends DOMException (#2084) (Tuesday, 29 January)
• Re: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Tuesday, 29 January)
• [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Tuesday, 29 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] Simulcast SDP clarifications (#2075) (Thursday, 24 January)
• Re: [webrtc-pc] Effect of RTCRtpSendParameters on Simulcast (#2073) (Thursday, 24 January)
• Re: [webrtc-pc] Describe how RIDs are added to a media section (#2071) (Thursday, 24 January)
• Re: [webrtc-pc] setCodecPreferences and RTX / RED / FEC codecs (#2069) (Thursday, 24 January)
• [webrtc-pc] new commits pushed by henbos (Thursday, 24 January)
• [webrtc-pc] Pull Request: RTCError extends DOMException (Thursday, 24 January)
• Re: [webrtc-stats] add stunserverconnectionstats (#372) (Wednesday, 23 January)
• Re: [webrtc-pc] Are IdP errors used? Mention of non-existing idpLoginUrl attribute. (#2083) (Wednesday, 23 January)
• [webrtc-pc] Are IdP errors used? Mention of non-existing idpLoginUrl attribute. (#2083) (Wednesday, 23 January)
• Re: [webrtc-pc] Make RTCError inherit from DOMException? (#2082) (Wednesday, 23 January)
• Re: [webrtc-pc] Make RTCError inherit from DOMException? (#2082) (Wednesday, 23 January)
• Re: [webrtc-pc] Simulcast SDP clarifications (#2075) (Tuesday, 22 January)
• Re: [webrtc-pc] RTCRtpReceiver.getParameters() clarification (#2032) (Tuesday, 22 January)
• Re: [webrtc-pc] RTCRtpReceiver.getParameters() clarification (#2032) (Tuesday, 22 January)
• [webrtc-pc] Pull Request: Add note about codec preferences in an answer (Tuesday, 22 January)
• [webrtc-pc] Pull Request: Fix typo in setCodecPreferences() steps (Tuesday, 22 January)
• [webrtc-pc] Typo in setCodecPreferences() (#2076) (Tuesday, 22 January)
• Re: [webrtc-pc] Clarify how codecs should be prioritized. (#2009) (Tuesday, 22 January)
• [webrtc-pc] RTCErrorEvent constructor's RTCErrorEventInit parameter should be optional (#2070) (Monday, 21 January)
• [webrtc-stats] new commits pushed by henbos (Monday, 21 January)
• [webrtc-pc] new commits pushed by henbos (Wednesday, 16 January)
• Closed: [webrtc-pc] Should RTCRtpTransceiver.setCodecPreferences() only refer to RTCRtpReceiver.getCapabilities(kind)? (#1998) (Tuesday, 15 January)
• Re: [webrtc-pc] Should RTCRtpTransceiver.setCodecPreferences() only refer to RTCRtpReceiver.getCapabilities(kind)? (#1998) (Tuesday, 15 January)
• Re: [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described (#1896) (Tuesday, 15 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• [webrtc-pc] new commits pushed by henbos (Monday, 14 January)
• Closed: [webrtc-pc] Update the editor's list to reflect who the editors are currently (#2051) (Monday, 14 January)
• [webrtc-pc] new commits pushed by henbos (Monday, 14 January)
• Closed: [webrtc-pc] Define what happens when you stop() an offerer tagged bundled transceiver (#2049) (Monday, 14 January)
• [webrtc-pc] new commits pushed by henbos (Monday, 14 January)
• Closed: [webrtc-pc] Describe which m= section is offerer tagged. (#2047) (Monday, 14 January)
• Re: [webrtc-pc] Don't require RTCRtpContributingSource.audioLevel to be present in some cases (#2046) (Thursday, 10 January)
• Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on? (#1858) (Thursday, 10 January)
• [webrtc-pc] Pull Request: Updated editor list (Thursday, 10 January)
• [webrtc-pc] Update the editor's list to reflect who the editors are currently (#2051) (Thursday, 10 January)
• Re: [webrtc-pc] Define what happens when you stop() an offerer tagged bundled transceiver (#2049) (Thursday, 10 January)
• Re: [webrtc-pc] Describing which media description is offerer tagged. (#2001) (Thursday, 10 January)
• [webrtc-pc] Pull Request: Stop bundled transceivers when the offerer tagged is stopped. (Thursday, 10 January)
• Re: [webrtc-pc] Describing which media description is offerer tagged. (#2001) (Thursday, 10 January)
• [webrtc-pc] Define what happens when you stop() an offerer tagged bundled transceiver (#2049) (Thursday, 10 January)
• [webrtc-pc] Pull Request: Define which m= section is offerer tagged. (Thursday, 10 January)
• Re: [webrtc-pc] Describing which media description is offerer tagged. (#2001) (Thursday, 10 January)
• [webrtc-pc] Describe which m= section is offerer tagged. (#2047) (Thursday, 10 January)
• [webrtc-pc] Don't require RTCRtpContributingSource.audioLevel to be present in some cases (#2046) (Thursday, 10 January)

Iñaki Baz Castillo via GitHub

• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• Closed: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Monday, 28 January)

Jan-Ivar Bruaroey via GitHub

• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Monday, 28 January)
• [mediacapture-main] Pull Request: Fix nonsense s/active document/responsible document/ in devicechange (editorial) (Friday, 25 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Friday, 25 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Friday, 25 January)
• Re: [mediacapture-main] enumerateDevices can be used to track user devices in background pages (#561) (Friday, 25 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Friday, 25 January)
• [mediacapture-main] Pull Request: MAY defer getUserMedia until page has focus. (Friday, 25 January)
• Re: [mediacapture-main] Should getUserMedia promise be resolved only on pages that have focus (#560) (Friday, 25 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Friday, 25 January)
• Re: [mediacapture-main] enumerateDevices can be used to track user devices in background pages (#561) (Thursday, 24 January)
• Re: [mediacapture-main] enumerateDevices can be used to track user devices in background pages (#561) (Thursday, 24 January)
• [mediacapture-main] Pull Request: Mitigate fingerprinting from OverconstrainedError in gUM(). (Thursday, 24 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Wednesday, 23 January)
• Re: [mediacapture-main] Should getUserMedia promise be resolved only on pages that have focus (#560) (Wednesday, 23 January)
• [webrtc-pc] new commits pushed by jan-ivar (Wednesday, 23 January)
• Closed: [webrtc-pc] Missing normative steps for determining codecs (#1982) (Wednesday, 23 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Wednesday, 23 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Tuesday, 22 January)
• Re: [webrtc-pc] Remove getDefaultIceServers(). (#2068) (Tuesday, 22 January)
• Re: [webrtc-pc] Add [[SendCodecs]] and [[ReceiveCodecs]] internal slots. (#2079) (Tuesday, 22 January)
• Re: [webrtc-pc] Add [[SendCodecs]] and [[ReceiveCodecs]] internal slots. (#2079) (Tuesday, 22 January)
• [webrtc-pc] Pull Request: Add [[SendCodecs]] and [[ReceiveCodecs]] internal slots. (Tuesday, 22 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Saturday, 19 January)
• [webrtc-pc] Pull Request: Remove getDefaultIceServers(). (Friday, 18 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Friday, 18 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Friday, 18 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Friday, 18 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Thursday, 17 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Wednesday, 16 January)
• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Tuesday, 15 January)
• [webrtc-stats] Pull Request: Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (Tuesday, 15 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Tuesday, 15 January)
• Re: [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries (#312) (Friday, 11 January)
• Re: [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries (#312) (Friday, 11 January)
• Closed: [mediacapture-record] Should stop(), pause(), resume() change state synchronously? (#123) (Thursday, 3 January)

Jesper via GitHub

• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Thursday, 31 January)
• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Wednesday, 30 January)
• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Wednesday, 30 January)
• [mediacapture-screen-share] Capturing audio-only (#100) (Monday, 28 January)

Jimmy Wärting via GitHub

• [webrtc-pc] Send transferable data (#2055) (Saturday, 12 January)

Lennart Grahl via GitHub

• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Wednesday, 30 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Tuesday, 29 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] WHATWG streams for data channel messages (#1732) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] Obtain user consent for one-way media and data use cases (#2012) (Wednesday, 23 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• Re: [webrtc-pc] Send transferable data (#2055) (Sunday, 13 January)

Marina Cicoea via GitHub

• Closed: [webrtc-pc] editorial: Typos in section 6.2 RTCDataChannel (#2059) (Wednesday, 16 January)
• [webrtc-pc] Pull Request: Fix typos in section 6.2 RTCDataChannel (Wednesday, 16 January)
• [webrtc-pc] editorial: Typos in section 6.2 RTCDataChannel (#2059) (Wednesday, 16 January)

Michael Tüxen via GitHub

• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)

Miguel Casas-Sanchez via GitHub

• Closed: [mediacapture-record] InvalidModificationError should be listed in section 4.3. Exception Summary (#163) (Wednesday, 30 January)
• [mediacapture-record] new commits pushed by yellowdoge (Wednesday, 30 January)
• [mediacapture-record] Pull Request: Added entry on InvalidModificationError; addresses #163 (Wednesday, 30 January)
• Closed: [mediacapture-record] Should a dataavailable event be dispatched in case there is no available data (#153) (Wednesday, 30 January)
• Re: [mediacapture-record] Should a dataavailable event be dispatched in case there is no available data (#153) (Wednesday, 30 January)
• Closed: [mediacapture-record] Required encoding types? (#145) (Thursday, 24 January)
• Re: [mediacapture-record] Required encoding types? (#145) (Thursday, 24 January)
• [mediacapture-record] new commits pushed by yellowdoge (Wednesday, 23 January)
• Closed: [mediacapture-record] Spec refers to "isolation properties" but this term is never explained (#138) (Wednesday, 23 January)
• [mediacapture-record] Pull Request: Linkify |isolation properties| and point it to webrtc-identity spec (Wednesday, 23 January)
• Closed: [mediacapture-record] Point to public-webrtc (#149) (Wednesday, 23 January)
• [mediacapture-record] new commits pushed by yellowdoge (Wednesday, 23 January)
• [mediacapture-record] Pull Request: Correct mailing list s/media-capture/webrtc/, #149 (Wednesday, 23 January)
• Closed: [mediacapture-record] timeslice should not be signed (#155) (Wednesday, 23 January)
• [mediacapture-record] new commits pushed by yellowdoge (Wednesday, 23 January)
• Re: [mediacapture-record] Make MediaRecorder's start() parameter |timeslice| unsigned (#159) (Wednesday, 23 January)
• [mediacapture-record] Pull Request: Make MediaRecorder's start() parameter |timeslice| unsigned (Wednesday, 23 January)
• Re: [mediacapture-image] Implementation status using torch on chrome under Windows 10 (#202) (Tuesday, 15 January)

na-g via GitHub

• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Friday, 25 January)

Nils Ohlmeier via GitHub

• Re: [webrtc-pc] Remove stopped transceivers from getTransceivers() (#2092) (Thursday, 31 January)

Philip Jägenstedt via GitHub

• Closed: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Wednesday, 23 January)
• Re: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Wednesday, 23 January)
• Re: [webrtc-pc] Make RTCError inherit from DOMException? (#2082) (Wednesday, 23 January)
• Re: [webrtc-pc] RTCErrorEvent constructor's RTCErrorEventInit parameter should be optional (#2070) (Monday, 21 January)
• [webrtc-stats] Pull Request: Fix capitalization mismatch in RTCRTPStreamStats (Monday, 21 January)
• Re: [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Friday, 18 January)
• [webrtc-stats] Mark up duplicate definition of RTCStats dictionary (#385) (Thursday, 17 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)
• [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)

Philipp Hancke via GitHub

• Re: [webrtc-pc] Remove stopped transceivers from getTransceivers() (#2092) (Thursday, 31 January)
• Re: [webrtc-pc] iceConnectionState, selectedCandidatePair and races in Chrome Canary (#2088) (Tuesday, 29 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Wednesday, 23 January)
• Re: [webrtc-pc] Can RTCDtlsTransport's iceTransport attribute change? (#2056) (Monday, 14 January)

Sergio Garcia Murillo via GitHub

• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Thursday, 31 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Wednesday, 30 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Wednesday, 30 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• Re: [webrtc-pc] Need something such as rtpSender.reset() (#2087) (Tuesday, 29 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] WHATWG streams for data channel messages (#1732) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Monday, 28 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Saturday, 26 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)
• Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086) (Friday, 25 January)

Shachar Zohar via GitHub

• Re: [webrtc-pc] Send transferable data (#2055) (Sunday, 13 January)

Varun Singh via GitHub

• Re: [webrtc-stats] Move (fir|pli|nack|sli)Count and qpSum out of baseclass to (in|out)bound (#384) (Wednesday, 23 January)

youennf via GitHub

• Re: [mediacapture-main] enumerateDevices is exposing devices labels for origins that are granted access once (#563) (Thursday, 31 January)
• Re: [mediacapture-screen-share] Capturing audio-only (#100) (Thursday, 31 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Monday, 28 January)
• [mediacapture-record] InvalidModificationError should be listed in section 4.3. Exception Summary (#163) (Saturday, 26 January)
• Re: [mediacapture-record] Recording a stream while adding/removing a track is not well defined (#151) (Saturday, 26 January)
• [mediacapture-record] Pull Request: Do not discard data in case track set change (Saturday, 26 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Friday, 25 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Friday, 25 January)
• Re: [mediacapture-main] enumerateDevices can be used to track user devices in background pages (#561) (Friday, 25 January)
• Re: [mediacapture-main] Should getUserMedia promise be resolved only on pages that have focus (#560) (Friday, 25 January)
• [mediacapture-main] Should a devicechange event be fired when the list of devices stays the same (#565) (Friday, 25 January)
• Re: [mediacapture-record] Recording a stream while adding/removing a track is not well defined (#151) (Friday, 25 January)
• Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• [mediacapture-main] enumerateDevices is exposing devices labels for origins that are granted access once (#563) (Thursday, 24 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Thursday, 24 January)
• [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562) (Thursday, 24 January)
• [mediacapture-main] enumerateDevices can be used to track user devices in background pages (#561) (Thursday, 24 January)
• [mediacapture-main] Should getUserMedia promise be resolved only on pages that have focus (#560) (Wednesday, 23 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Wednesday, 23 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Wednesday, 23 January)
• Re: [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Tuesday, 22 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Saturday, 19 January)
• [mediacapture-main] Spec does no handle fingerprinting related to exposing non default capture devices (#559) (Friday, 18 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Friday, 18 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Thursday, 17 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Thursday, 17 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Tuesday, 15 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Tuesday, 15 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Tuesday, 15 January)
• Re: [mediacapture-main] Should we allow empty string device IDs? (#551) (Thursday, 10 January)

Last message date: Thursday, 31 January 2019 18:39:50 UTC