Saturday, 31 August 2019
- [mediacapture-screen-share] Pull Request: Resolve optional/default error
- [mediacapture-screen-share] Respec error (#112)
- [mediacapture-screen-share] Pull Request: Add Henrik and Jan-Ivar as editors
- Closed: [webrtc-pc] Status of Document: Update "features at risk" list (#2275)
- [webrtc-pc] new commits pushed by aboba
Friday, 30 August 2019
- Re: [webrtc-pc] Timing of setRemoteDescription's identity validation is unclear (#2173)
- Re: [webrtc-stats] OPUS -- Exposing SILK or CELT mode in getStats (#432)
- Re: [webrtc-stats] Measuring background noise (energy) (#465)
- [webrtc-pc] new commits pushed by jan-ivar
- Closed: [webrtc-pc] Properly define origin (and handling thereof) for PeerConnection (#1969)
- Re: [webrtc-pc] Order of multiple RTCDataChannel.send calls in case of blobs (#2215)
- Re: [webrtc-pc] Order of multiple RTCDataChannel.send calls in case of blobs (#2215)
- Re: [webrtc-pc] Clarify SRD() won't reject on identity failure wo/target peer identity. (#2250)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [webrtc-stats] OPUS -- Exposing SILK or CELT mode in getStats (#432)
- Re: [webrtc-pc] Order of multiple RTCDataChannel.send calls in case of blobs (#2215)
- [mediacapture-main] Pull Request: Clarify that devicechange event is skippable if there is no change of devices
- Re: [mediacapture-main] oldList definition in enumerateDevices is unclear (#604)
- [mediacapture-main] Pull Request: Remove oldList and make it clear that groupId scope is the document
- Re: [webrtc-pc] Clarify that blob send order should respect the send call order (#2286)
- [webrtc-pc] Pull Request: Clarify that blob send order should respect the send call order
- [webrtc-pc] Pull Request: Simplify checks in insertDTMF since some of them are redundant
- Re: [webrtc-pc] Checks in https://w3c.github.io/webrtc-pc/#dom-RTCDTMFSender-insertDTMF could be simplified (#2254)
- Re: [webrtc-stats] Exposing RTCIceCandidateStats.networkType might trigger fingerprinting (#374)
- Re: [mediacapture-record] Add replaceTrack method to MediaStream (#167)
Thursday, 29 August 2019
- Re: [mediacapture-record] Add replaceTrack method to MediaStream (#167)
- Re: [mediacapture-record] Add replaceTrack method to MediaStream (#167)
- Re: [mediacapture-fromelement] MediaStreamTrack does not dispatch "ended" event at Chromium when src of HTMLMediaElement is changed, Firefox does dispatch "ended" event; which implementation is correct? (#78)
- Closed: [mediacapture-fromelement] MediaStreamTrack does not dispatch "ended" event at Chromium when src of HTMLMediaElement is changed, Firefox does dispatch "ended" event; which implementation is correct? (#78)
- Re: [webrtc-stats] Exposing RTCIceCandidateStats.networkType might trigger fingerprinting (#374)
- Re: [webrtc-stats] Issues with replaceTrack, will statsended fire or give me what I want. (#472)
- Re: [webrtc-stats] Move packetsDiscardedOnSend to RTCIceCandidatePairStats (#438)
- Re: [webrtc-stats] The spec has incorrect assumptions abound SR and RR (#433)
- Re: [webrtc-stats] OPUS -- Exposing SILK or CELT mode in getStats (#432)
- Re: [webrtc-stats] RTCVideo*Stats: Video Device Errors (#430)
- Re: [webrtc-stats] Request to add neteq waiting time to stats report (#427)
- Re: [webrtc-stats] RTCRemoteInboundRtpStreamStats: total round trip time (#426)
- Re: [webrtc-stats] RTCRemoteInboundRtpStreamStats: total round trip time (#426)
- Re: [webrtc-stats] Receiver attachment stats missing (#424)
- Re: [webrtc-stats] RTC[Audio/Video]SenderStats should have mid (#396)
- Re: [webrtc-stats] Should we move track/sender/receiver to the obsolete section? (#479)
- Re: [webrtc-stats] Should we have transceiver stats? (#478)
- Re: [webrtc-stats] Impact on Track Stats because of moving stats from sender/receiver to appropriate in/outbound rtp (#403)
- Closed: [webrtc-stats] Impact on Track Stats because of moving stats from sender/receiver to appropriate in/outbound rtp (#403)
- Re: [webrtc-stats] Should we move track/sender/receiver to the obsolete section? (#479)
- Re: [webrtc-stats] What should we do about onstatsended? (#480)
- [webrtc-stats] What should we do about onstatsended? (#480)
- Re: [webrtc-stats] Should we move track/sender/receiver to the obsolete section? (#479)
- [webrtc-stats] Should we move track/sender/receiver to the obsolete section? (#479)
- Re: [webrtc-stats] Should we have transceiver stats? (#478)
- Re: [webrtc-stats] targetBitrate should not be "measured over 1 second window" (#423)
- Re: [webrtc-stats] Impact on Track Stats because of moving stats from sender/receiver to appropriate in/outbound rtp (#403)
- Re: [webrtc-stats] Add SVC stats in RTC[In/Out]boundRtpStreamStats (#401)
- Re: [webrtc-stats] Add RTCOutboundRtpStreamStats.framesDiscardedOnSend (#397)
- Re: [webrtc-stats] RTC[Audio/Video]SenderStats should have mid (#396)
- [webrtc-stats] Should we have transceiver stats? (#478)
- Re: [webrtc-stats] Correlating RTCInboundRtpStreamStats with simulcast streams (#393)
- Re: [mediacapture-record] Add replaceTrack method to MediaStream (#167)
- [mediacapture-output] Selecting audio output in case device info permission is not granted (#83)
- [webrtc-pc] Should peer identity specific steps be marked as "Feature at risk" (#2284)
- Re: [webrtc-pc] Merge the steps for updating candidate pair and ice transport state (#2283)
- [webrtc-pc] Merge the steps for updating candidate pair and ice transport state (#2283)
- Re: [webrtc-pc] RTCIceTransport selected candidate pair behavior when changing state (#2276)
- Closed: [webrtc-pc] Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (#2260)
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Clarify SRD() won't reject on identity failure wo/target peer identity. (#2250)
- Re: [mediacapture-main] When is a MediaStream playing? (#615)
- Re: [webrtc-stats] framesDecoded is on both "receiver" and "inbound-rtp" (#392)
- Closed: [webrtc-stats] framesDecoded is on both "receiver" and "inbound-rtp" (#392)
- Re: [webrtc-stats] audioLevel can be removed from "track"|"receiver"|"sender" stats (#391)
- Re: [mediacapture-main] When is a MediaStream playing? (#615)
- Re: [webrtc-stats] Is exposing a remote peer IP address through RTCIceCandidateStats.address a privacy issue (#375)
- Closed: [webrtc-stats] Is exposing a remote peer IP address through RTCIceCandidateStats.address a privacy issue (#375)
- Re: [webrtc-stats] Exposing RTCIceCandidateStats.networkType might trigger fingerprinting (#374)
- Re: [webrtc-stats] Call out which stats are expected to trigger StatsEnded events (#366)
- Closed: [webrtc-stats] Call out which stats are expected to trigger StatsEnded events (#366)
- Re: [webrtc-stats] identifying the ice generation of a candidate pair (#358)
- Re: [webrtc-stats] identifying the ice generation of a candidate pair (#358)
- Re: [webrtc-stats] References to "objectDeleted" can be removed (#357)
- Closed: [webrtc-stats] References to "objectDeleted" can be removed (#357)
- Re: [mediacapture-depth] Unable to use MediaRecorder | ImageCapture.takePhoto() on a depth stream (#173)
- Closed: [webrtc-stats] RTCIceCandidateStats.deleted can be removed (#356)
- Re: [webrtc-stats] RTCIceCandidateStats.deleted can be removed (#356)
- Re: [webrtc-stats] Input/output resolution and audio energy (#353)
- Closed: [webrtc-stats] Input/output resolution and audio energy (#353)
- Re: [mediacapture-main] When is a MediaStream playing? (#615)
- [webrtc-pc] Update to constructor operations (#2282)
- [mediacapture-main] Update to constructor operations (#616)
- [mediacapture-record] Update to constructor operations (#182)
Wednesday, 28 August 2019
- [mediacapture-main] When is a MediaStream playing? (#615)
- [mediacapture-record] MediaStream does not expose a RecordingState (#181)
- [mediacapture-main] new commits pushed by aboba
- [mediacapture-main] new commits pushed by aboba
- [mediacapture-main] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- [webrtc-pc] Wrong RTC referenced by rtpTimestamp (#2281)
- Closed: [webrtc-stats] Add counter for number of times resolution changes (#476)
- [webrtc-stats] new commits pushed by henbos
- Re: [webrtc-stats] RTCOutboundRtpStreamStats.qualityLimitationResolutionChanges added. (#477)
Tuesday, 27 August 2019
- [webrtc-pc] Pull Request: Update "Features at risk"
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [webrtc-stats] RTCOutboundRtpStreamStats.qualityLimitationResolutionChanges added. (#477)
- Re: [webrtc-stats] RTCOutboundRtpStreamStats.qualityLimitationResolutionChanges added. (#477)
- [webrtc-stats] Pull Request: RTCOutboundRtpStreamStats.qualityLimitationResolutionChanges added.
- [webrtc-stats] Add counter for number of times resolution changes (#476)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
Monday, 26 August 2019
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [webrtc-stats] Interframe delay stat for video receive stream. (#229)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] Move enumerateDevices behind permission (#612)
Sunday, 25 August 2019
- Re: [mediacapture-record] Input video track width and height MUST be recorded and playable (#173)
- Re: [mediacapture-record] Input video track width and height MUST be recorded and playable (#173)
Saturday, 24 August 2019
- Re: [mediacapture-main] Remove or rename 'volume' (#585)
- Re: [mediacapture-main] Move enumerateDevices behind permission (#612)
Friday, 23 August 2019
- Re: [mediacapture-image] Add dictionary default value (#215)
- [mediacapture-image] Pull Request: Add dictionary default value
- Re: [mediacapture-screen-share] Add dictionary default value (#110)
- [mediacapture-screen-share] Pull Request: Add dictionary default value
- Closed: [mediacapture-main] Why does unmute event take between 30 to 60 seconds to dispatch? Does a canonical procedure exist to estimate when unmute will be dispatched? (#614)
Thursday, 22 August 2019
- Re: [webrtc-pc] RTCIceTransport selected candidate pair behavior when changing state (#2276)
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] Meta: Create rules for using the Github "project" feature (#2279)
- Re: [mediacapture-main] Why does unmute event take between 30 to 60 seconds to dispatch? Does a canonical procedure exist to estimate when unmute will be dispatched? (#614)
- Re: [mediacapture-main] Why does unmute event take between 30 to 60 seconds to dispatch? Does a canonical procedure exist to estimate when unmute will be dispatched? (#614)
- Re: [mediacapture-main] Volume attributes for audio MediaStreamTracks? (#523)
- Closed: [mediacapture-main] Volume attributes for audio MediaStreamTracks? (#523)
- Re: [mediacapture-main] Volume attributes for audio MediaStreamTracks? (#523)
- Re: [mediacapture-main] audioElement should ignore video tracks in a stream wrt ended. (#520)
- Closed: [mediacapture-main] applyConstraints algorithm threading issues (editorial) (#530)
- Re: [mediacapture-main] applyConstraints algorithm threading issues (editorial) (#530)
- Closed: [mediacapture-main] NotAllowedError or SecurityError over Feature Policy? (#545)
- Re: [webrtc-pc] RTCIceTransport selected candidate pair behavior when changing state (#2276)
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] Meta: Create rules for using the Github "project" feature (#2279)
- [webrtc-pc] Pull Request: Describe how to use the github project feature
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- [webrtc-pc] Update spec to new IDL syntax for optional dictionaries (#2277)
Wednesday, 21 August 2019
- Re: [mediacapture-main] Why does unmute event take between 30 to 60 seconds to dispatch? Does a canonical procedure exist to estimate when unmute will be dispatched? (#614)
- [mediacapture-main] Why does unmute event take between 30 to 60 seconds to dispatch? Does a canonical procedure exist to estimate when unmute will be dispatched? (#614)
- [mediacapture-record] Update spec to new IDL syntax for optional dictionaries (#180)
- [mediacapture-main] Update spec to new IDL syntax for optional dictionaries (#613)
- [mediacapture-image] Update spec to new IDL syntax for optional dictionaries (#214)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] Add metric for ICE reroutes (#474)
- [mediacapture-main] Move enumerateDevices behind permission (#612)
- Re: [webrtc-stats] Add RTCTransportStats.selectedCandidatePairChanges (#475)
- Re: [webrtc-stats] Add RTCTransportStats.selectedCandidatePairChanges (#475)
Tuesday, 20 August 2019
- Re: [webrtc-stats] Issues with replaceTrack, will statsended fire or give me what I want. (#472)
- Re: [webrtc-stats] Adds RTCTransportStats.selectedCandidatePairChanges (#475)
Monday, 19 August 2019
- Re: [webrtc-stats] Issues with replaceTrack, will statsended fire or give me what I want. (#472)
- Re: [webrtc-stats] Rethinking "sender" and "receiver" stats (#471)
- Re: [webrtc-stats] RTC[Audio/Video]SenderStats should have mid (#396)
- Re: [webrtc-stats] Rethinking "sender" and "receiver" stats (#471)
- Re: [webrtc-stats] Add metric for ICE reroutes (#474)
- Re: [webrtc-stats] Add metric for ICE reroutes (#474)
- Re: [webrtc-stats] Adds RTCTransportStats.selectedCandidatePairChanges (#475)
- [webrtc-stats] Pull Request: Adds RTCTransportStats.selectedCandidatePairChanges
- [webrtc-stats] Add metric for ICE reroutes (#474)
Friday, 16 August 2019
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- [webrtc-pc] Pull Request: RTCIceTransport selected candidate pair behavior when changing state
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- [webrtc-stats] new commits pushed by vr000m
- Closed: [webrtc-stats] We should move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats (#445)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [webrtc-stats] Move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats.[decoder/encoder]Implementation (#473)
- [webrtc-stats] Pull Request: Move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats.[decoder/encoder]Implementation
- Re: [webrtc-stats] We should move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats (#445)
- Re: [webrtc-stats] We should move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats (#445)
- Re: [webrtc-stats] We should move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats (#445)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-screen-share] Should the permissions UI be the first captured frame? (#108)
- [mediacapture-record] Add method that allows user specification of which tracks go with what number in the container-dependent ordering (#179)
Thursday, 15 August 2019
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- [webrtc-pc] Status of Document: Update "features at risk" list (#2275)
- Re: [webrtc-pc] Spec steps on stop() underestimate BUNDLE problem. (#2176)
- Closed: [webrtc-pc] Spec steps on stop() underestimate BUNDLE problem. (#2176)
- Re: [webrtc-pc] createOffer does not guard against "have-remote-offer" (#2145)
- Closed: [webrtc-pc] createOffer does not guard against "have-remote-offer" (#2145)
- Closed: [webrtc-pc] stuns: usage in examples (#2270)
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] Pull Request: Change "stuns" to "stun" in examples
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-screen-share] Should the permissions UI be the first captured frame? (#108)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Closed: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-main] MediaTrackSettings lacks support of channel layout (#605)
- Re: [mediacapture-main] MediaTrackSettings lacks support of channel layout (#605)
- Closed: [mediacapture-main] Remove "The relative order of the tracks in the set is User Agent defined and the API will never put any requirements on the order.", et al. (#611)
- Closed: [mediacapture-main] Violation. (#610)
- Re: [mediacapture-main] Violation. (#610)
- [mediacapture-main] new commits pushed by henbos
- [mediacapture-main] new commits pushed by henbos
- Closed: [webrtc-pc] No procedure for the ICE failed state (#2004)
- Closed: [webrtc-pc] Mark voiceActivityDetection and dtx as Feature At Risk (Was: Is voiceActivityDetection still needed?) (#2236)
- Closed: [webrtc-pc] Mark Oauth as a "feature at risk" (#2246)
- Closed: [webrtc-pc] Mark getSupportedAlgorithms as a "feature at risk" (#2255)
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] example 14: render before verifying the remote fingerprint? (#1709)
- Closed: [webrtc-pc] Example 14 never sends any media (#1708)
- Re: [webrtc-pc] RTCIceTransport selected candidate pair behavior when changing state (#2269)
- [webrtc-pc] ICE restart and terminal RTCIceTransport.state "failed" state (#2273)
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Too many test links in the spec, some redundant (#2161)
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk" (#2258)
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by henbos
- [webrtc-pc] new commits pushed by henbos
- Re: [webrtc-pc] Add initialization of DataChannelId on connection (#2222)
- Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)
- Re: [mediacapture-main] Is enumerateDevices list order significant? (#608)
- Re: [mediacapture-main] Remove "The relative order of the tracks in the set is User Agent defined and the API will never put any requirements on the order.", et al. (#611)
- Re: [webrtc-pc] Checks in https://w3c.github.io/webrtc-pc/#dom-RTCDTMFSender-insertDTMF could be simplified (#2254)
- Closed: [mediacapture-record] Add method MediaRecorder.restart considering this use case. (#178)
Wednesday, 14 August 2019
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint? (#1709)
- [webrtc-pc] Pull Request: Change "stuns" to "stun" in examples
- Re: [webrtc-pc] RTCIceTransport selected candidate pair behavior when changing state (#2269)
- Re: [mediacapture-main] Interpret the empty string as if the constraint is not specified (#595)
- Re: [mediacapture-main] Recommend UUID for deviceId and groupId (#591)
- Re: [webrtc-pc] Permission API for receive-only media and data use cases (#2175)
- Re: [webrtc-stats] Rethinking "sender" and "receiver" stats (#471)
- [webrtc-stats] Issues with replaceTrack, will statsended fire or give me what I want. (#472)
- Re: [webrtc-stats] Rethinking "sender" and "receiver" stats (#471)
- [webrtc-stats] Rethinking "sender" and "receiver" stats (#471)
- [webrtc-stats] RTCMediaStreamStats can be made obsolete (#470)
- Re: [webrtc-stats] Deleted was removed in #462, was not added to Obsolete section (#467)
- Re: [webrtc-stats] New Respec issues (#468)
- Closed: [webrtc-stats] New Respec issues (#468)
- Re: [webrtc-stats] New Respec issues (#468)
- [webrtc-stats] new commits pushed by henbos
- Re: [webrtc-stats] Fix respec issues (#469)
- [webrtc-stats] Pull Request: Fix respec issues
- Re: [webrtc-stats] New Respec issues (#468)
- Closed: [webrtc-stats] Move all stream stats from the "sender"/"receiver" stats (#402)
- Re: [webrtc-stats] Move all stream stats from the "sender"/"receiver" stats (#402)
- [webrtc-stats] new commits pushed by henbos
- Re: [webrtc-stats] Move "receiver" stats to "inbound-rtp" (#466)
- [webrtc-stats] New Respec issues (#468)
- [webrtc-stats] Deleted was removed in #462, was not added to Obsolete section (#467)
- Re: [webrtc-stats] Move "receiver" stats to "inbound-rtp" (#466)
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-pc] Permission API for receive-only media and data use cases (#2175)
- Re: [webrtc-pc] Timing of setRemoteDescription's identity validation is unclear (#2173)
- Re: [webrtc-pc] Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk" (#2259)
- Re: [webrtc-pc] Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (#2261)
- Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture (#1575)
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint? (#1709)
- [webrtc-pc] Pull Request: Remove example on media before signaling
- Re: [webrtc-pc] Example 14 never sends any media (#1708)
- Re: [webrtc-pc] Clarify example on example with media before signaling (#2266)
- Re: [webrtc-pc] Clarify example on example with media before signaling (#2266)
- [webrtc-pc] stuns: usage in examples (#2270)
- Re: [webrtc-pc] Clarify example on example with media before signaling (#2266)
Tuesday, 13 August 2019
- [webrtc-pc] Pull Request: RTCIceTransport selected candidate pair behavior when changing state
- Re: [webrtc-pc] RTCIceTransport selected candidate pair behavior when changing state (#1981)
- Closed: [webrtc-pc] WHATWG streams for data channel messages (#1732)
- Re: [webrtc-pc] WHATWG streams for data channel messages (#1732)
- Re: [webrtc-pc] WHATWG streams for data channel messages (#1732)
- [webrtc-pc] Pull Request: Effect of ICE failed state
- Re: [webrtc-pc] degradationPreference is under-specified (#2248)
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] RTCDataChannel section structure (#1847)
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Use consistent internal slot terminology (editorial) (#2226)
- Re: [webrtc-pc] Clarify example on example with media before signaling (#2266)
- [webrtc-stats] Pull Request: Move "receiver" stats to "inbound-rtp"
Monday, 12 August 2019
- Re: [webrtc-pc] Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (#2261)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- [webrtc-pc] Pull Request: Properly sort simulcast layers in example by size
- [webrtc-pc] Pull Request: Clarify example on example with media before signaling
- [webrtc-pc] Pull Request: Add sub-structure to data channel description
- [webrtc-pc] Pull Request: Use consistent notation for internal slots
- Re: [webrtc-pc] Mark Oauth as a "feature at risk" (#2246)
- [webrtc-pc] Pull Request: Update test annotations with WPT updates merged since end of April
Sunday, 11 August 2019
Saturday, 10 August 2019
- Re: [webrtc-pc] getSelectedCandidatePair needs special treatment for PRFLX candidates (#2134)
- Closed: [webrtc-pc] getSelectedCandidatePair needs special treatment for PRFLX candidates (#2134)
- Re: [webrtc-pc] degradationPreference is under-specified (#2248)
Friday, 9 August 2019
- Re: [webrtc-pc] degradationPreference is under-specified (#2248)
- Re: [webrtc-pc] SLD({type: "offer"}) wo/createOffer should be InvalidModificationError (#2143)
- Closed: [webrtc-pc] SLD({type: "offer"}) wo/createOffer should be InvalidModificationError (#2143)
- [webrtc-pc] Pull Request: Hide test annotations by default
- Re: [webrtc-pc] Set the configuration is unnecessarily checking for some members being set (#2142)
- Closed: [webrtc-pc] Set the configuration is unnecessarily checking for some members being set (#2142)
- Re: [webrtc-pc] Redundant queuing in connection state computations. (#2020)
- Re: [webrtc-pc] Should WPT webrtc folder be renamed to webrtc-pc (#2026)
- Closed: [webrtc-pc] Should WPT webrtc folder be renamed to webrtc-pc (#2026)
- Re: [webrtc-pc] Spec steps on stop() underestimate BUNDLE problem. (#2176)
- Re: [webrtc-pc] createOffer does not guard against "have-remote-offer" (#2145)
- Re: [webrtc-pc] getSelectedCandidatePair needs special treatment for PRFLX candidates (#2134)
- Closed: [webrtc-pc] Clarifications of certificate expiry (#2045)
- Re: [webrtc-pc] Clarifications of certificate expiry (#2045)
Thursday, 8 August 2019
- Re: [webrtc-pc] Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (#2260)
- Re: [webrtc-pc] RTCDTMFToneChangeEventInit.tone is required (#2253)
- Re: [webrtc-pc] Clarify "multiple sources of media stitched together" at Note describing replaceTrack (#2171)
- Closed: [webrtc-pc] Clarify "multiple sources of media stitched together" at Note describing replaceTrack (#2171)
- Re: [webrtc-pc] Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (#2260)
- [webrtc-pc] Pull Request: Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk"
- [webrtc-pc] Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (#2260)
- Re: [webrtc-pc] reducing audio packet rate while track is disabled (#1764)
- [webrtc-pc] Pull Request: Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk"
- [webrtc-pc] Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk" (#2258)
Tuesday, 6 August 2019
Monday, 5 August 2019
- [webrtc-pc] Pull Request: Mark getSupportedAlgorithms as a "feature at risk"
- [webrtc-pc] Mark getSupportedAlgorithms as a "feature at risk" (#2255)
- Re: [webrtc-pc] Permission API for receive-only media and data use cases (#2175)
- Re: [webrtc-pc] Clarify that getSynchronizationSources() should return information even if the track has no sink (<video> tag) (#2240)
- [webrtc-pc] Checks in https://w3c.github.io/webrtc-pc/#dom-RTCDTMFSender-insertDTMF could be simplified (#2254)
- [webrtc-pc] RTCDTMFToneChangeEventInit.tone is required (#2253)
Sunday, 4 August 2019
Saturday, 3 August 2019
Friday, 2 August 2019
- [webrtc-pc] Pull Request: Clarify SRD() won't reject on identity failure wo/target peer identity.
- Re: [webrtc-pc] Add a [[DocumentOrigin]] internal slot to RTCPeerConnection. (#2249)
- Re: [webrtc-pc] Clarify that getSynchronizationSources() should return information even if the track has no sink (<video> tag) (#2240)
- Re: [mediacapture-screen-share] The user agent should be allowed to change sources after getDisplayMedia() resolves (#81)
- Re: [webrtc-pc] Clarify that getSynchronizationSources() should return information even if the track has no sink (<video> tag) (#2240)
- [webrtc-pc] Pull Request: Add a [[DocumentOrigin]] internal slot to RTCPeerConnection.
- Re: [mediacapture-record] Ability to tell MediaRecorder to maximize frame rate (#177)
- Re: [webrtc-pc] degradationPreference is under-specified (#2248)
- [mediacapture-record] new commits pushed by jan-ivar
- Closed: [mediacapture-record] What are the default bitrate attribute values? (#169)
- Re: [mediacapture-record] Input video track width and height MUST be recorded and playable (#173)
- Re: [mediacapture-record] Define behavior for all bitsPerSecond attributes (#175)
- Re: [webrtc-pc] Clarify that getSynchronizationSources() should return information even if the track has no sink (<video> tag) (#2240)
- Re: [mediacapture-record] Input video track width and height MUST be recorded and playable (#173)
- Re: [mediacapture-record] Ability to tell MediaRecorder to maximize frame rate (#177)
- Re: [webrtc-stats] OPUS -- Exposing SILK or CELT mode in getStats (#432)
- Re: [mediacapture-record] Ability to tell MediaRecorder to maximize frame rate (#177)
Thursday, 1 August 2019
- [mediacapture-record] Ability to tell MediaRecorder to maximize frame rate (#177)
- [webrtc-pc] degradationPreference is under-specified (#2248)
- Re: [mediacapture-screen-share] The user agent should be allowed to change sources after getDisplayMedia() resolves (#81)
- Re: [webrtc-pc] Clarify that getSynchronizationSources() should return information even if the track has no sink (<video> tag) (#2240)
- Re: [mediacapture-screen-share] The user agent should be allowed to change sources after getDisplayMedia() resolves (#81)
- Re: [webrtc-pc] Section 4.3.1: operations queue and setDescription (#1277)
- Closed: [webrtc-pc] Section 4.3.1: operations queue and setDescription (#1277)
- [webrtc-pc] Pull Request: Mark OAuth as a "feature at risk"
- [webrtc-pc] Mark Oauth as a "feature at risk" (#2246)
- [webrtc-pc] Pull Request: Mark VAD and dtx as "features at risk"
- Re: [webrtc-pc] Codify refusing to generate an empty Offer (#1745)
- Closed: [webrtc-pc] Codify refusing to generate an empty Offer (#1745)
- Closed: [webrtc-pc] Send transferable data (#2055)
- Re: [webrtc-pc] Send transferable data (#2055)
- Re: [webrtc-pc] Order of multiple RTCDataChannel.send calls in case of blobs (#2215)
- Closed: [webrtc-pc] API for codec performance (#2241)
- Re: [webrtc-pc] API for codec performance (#2241)
- Closed: [webrtc-pc] RTCIceTransport.getRemoteCandidates() does not return prflx candidates (#2124)
- Closed: [webrtc-pc] callback-based https://w3c.github.io/webrtc-pc/#method-extensions are not covered by WPT tests (#2022)
- Re: [webrtc-pc] callback-based https://w3c.github.io/webrtc-pc/#method-extensions are not covered by WPT tests (#2022)
- Closed: [webrtc-pc] Missing CNAME in RID based simulcast offer (#2114)
- Closed: [webrtc-pc] More simulcast examples (#2035)
- Re: [webrtc-pc] Are sinks a prerequisite for decoding? getSynchronizationSources() without <video> (#2240)
- Re: [webrtc-pc] Make possible to select TURN allocation address family (to avoid IPv6 confusion) (#1972)
- Closed: [webrtc-pc] Make possible to select TURN allocation address family (to avoid IPv6 confusion) (#1972)
- Closed: [webrtc-pc] transceiver.direction doesn’t respond, if out-of-sync. (#1940)
- Closed: [webrtc-pc] transceiver.direction doesn’t respond, if out-of-sync. (#1940)
- Re: [webrtc-pc] Codify refusing to generate an empty Offer (#1745)
- Re: [mediacapture-screen-share] Screenshot (still image) capability (#107)
- Closed: [mediacapture-screen-share] Screenshot (still image) capability (#107)
- [mediacapture-record] new commits pushed by aboba
- Closed: [mediacapture-record] Clarification needed for mime type handling (#170)
- Re: [webrtc-pc] API for codec performance (#2241)
- Closed: [webrtc-pc] Control surface for header extensions (#2243)
- Re: [webrtc-pc] Nulling mid when m-line is recycled is surprising. (#2238)
- Closed: [webrtc-pc] Nulling mid when m-line is recycled is surprising. (#2238)
- Re: [webrtc-pc] Control surface for header extensions (#2243)
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Permission API for receive-only media and data use cases (#2175)
- Re: [webrtc-pc] Nulling mid when m-line is recycled is surprising. (#2238)
- Re: [webrtc-pc] API for codec performance (#2241)
- Re: [webrtc-pc] API for codec performance (#2241)