[webrtc-pc] Section 8.6 Mandatory To Implement Stats, (#2484)
[mst-content-hint] highly detailed text in video content (#35)
[webrtc-pc] What is the behavior when the RTP extension for rotation is sent? (#2483)
Closed: [mediacapture-main] Width and height of MediaStreamTrack (#647)
Re: [mediacapture-main] Handling of rotation for camera capture streams (#660)
Re: [mediacapture-main] Width and height of MediaStreamTrack (#647)
[webrtc-pc] Section 6.2 RTCDataChannel, Attributes (#2482)
[mediacapture-main] Pull Request: Added support for new "category" constraint for audio
- Re: [mediacapture-main] Added support for new "category" constraint for audio (#664)
- Re: [mediacapture-main] Added support for new "category" constraint for audio (#664)
- Re: [mediacapture-main] Added support for new "category" constraint for audio (#664)
- Re: [mediacapture-main] Added support for new "category" constraint for audio (#664)
[mediacapture-main] Pull Request: Added support for new "category" constraint for audio
[webrtc-ice] Pull Request: Add initial FlexICE methods and attributes
Re: [webrtc-ice] Add initial FlexICE methods and attributes (#22)
Re: [webrtc-stats] RTCIceServerStats relayProtocol (#519)
[webrtc-extensions] new commits pushed by henbos
[webrtc-extensions] Pull Request: Adding A/V-sync and one-way delay related data to RTCRtpContributingSource
[webrtc-extensions] Add RTP captureTimestamp and sendCaptureTimeOffset for A/V-sync and one-way delay (#32)
[webrtc-pc] Pull Request: Simulcast functionality clarification
[mediacapture-main] Pull Request: Relinquish device when all tracks are muted or disabled.
- Re: [mediacapture-main] Relinquish device when all tracks are muted or disabled. (#662)
- Re: [mediacapture-main] Relinquish device when all tracks are muted or disabled. (#662)
- Re: [mediacapture-main] Relinquish device when all tracks are muted or disabled. (#662)
- Re: [mediacapture-main] Relinquish device when all tracks are muted or disabled. (#662)
Re: [webrtc-extensions] Add API for exposing codec HW capabilities (hardwareAccelerated) (#21)
- Re: [webrtc-extensions] Add API for exposing codec HW capabilities (hardwareAccelerated) (#21)
- Re: [webrtc-extensions] Add API for exposing codec HW capabilities (hardwareAccelerated) (#21)
- Re: [webrtc-extensions] Add API for exposing codec HW capabilities (hardwareAccelerated) (#21)
- Re: [webrtc-extensions] Add API for exposing codec HW capabilities (hardwareAccelerated) (#21)
- Re: [webrtc-extensions] Add API for exposing codec HW capabilities (hardwareAccelerated) (#21)
[webrtc-extensions] new commits pushed by henbos
Closed: [webrtc-extensions] Add API for controlling RTP header extension negotiation and usage (#24)
[webrtc-extensions] Need more submitters to this repo (#31)
- Closed: [webrtc-extensions] Need more submitters to this repo (#31)
- Re: [webrtc-extensions] Need more submitters to this repo (#31)
[webrtc-pc] Section 5.4.1 Simulcast functionality (#2480)
[webrtc-pc] new commits pushed by henbos
[webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)
- Re: [webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)
- Re: [webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)
- Closed: [webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)
- Re: [webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)
[mediacapture-main] What direction should a stopped transceiver have? (#661)
- Closed: [mediacapture-main] What direction should a stopped transceiver have? (#661)
- Re: [mediacapture-main] What direction should a stopped transceiver have? (#661)
[webrtc-stats] Pull Request: RTCSctpTransportStats additional stats
- Re: [webrtc-stats] RTCSctpTransportStats additional stats (#551)
- Re: [webrtc-stats] RTCSctpTransportStats additional stats (#551)
- Re: [webrtc-stats] RTCSctpTransportStats additional stats (#551)
- Re: [webrtc-stats] RTCSctpTransportStats additional stats (#551)
Re: [mediacapture-record] Multi-blob encoding (#192)
[webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
- Re: [webrtc-stats] Stats API should require additional permission / user opt-in (#550)
[webrtc-pc] Pull Request: Queue then chain steps to update the negotiation-needed flag.
[webrtc-pc] negotiationneeded may still fire when it shouldn't (#2477)
- Re: [webrtc-pc] negotiationneeded may still fire when it shouldn't (#2477)
- Re: [webrtc-pc] negotiationneeded may still fire when it shouldn't (#2477)
- Closed: [webrtc-pc] negotiationneeded may still fire when it shouldn't (#2477)
[mediacapture-image] "Tap to auto-focus" feature (#217)
[webrtc-extensions] define playoutDelayHint aggressiveness (#30)
[webrtc-pc] JSEP reads & modifies transceivers in parallel, causing racy behavior. (#2476)
- Re: [webrtc-pc] JSEP reads & modifies transceivers in parallel, causing racy behavior. (#2476)
- Re: [webrtc-pc] JSEP reads & modifies transceivers in parallel, causing racy behavior. (#2476)
- Re: [webrtc-pc] JSEP reads & modifies transceivers in parallel, causing racy behavior. (#2476)
Re: [webrtc-pc] How to refer to "disassociated transcievers" (#2455)
Closed: [webrtc-pc] How to refer to "disassociated transcievers" (#2455)
[mediacapture-record] What is the difference between start/stop and pause/resume methods? (#195)
- Re: [mediacapture-record] What is the "important"difference between start/stop and pause/resume methods? (#195)
- Re: [mediacapture-record] What is the "important"difference between start/stop and pause/resume methods? (#195)
- Re: [mediacapture-record] What is the "important"difference between start/stop and pause/resume methods? (#195)
- Re: [mediacapture-record] What is the "important"difference between start/stop and pause/resume methods? (#195)
[webrtc-pc] new commits pushed by dontcallmedom
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] new commits pushed by henbos
[webrtc-extensions] Pull Request: Adding A/V-sync and one-way delay related data to
- Re: [webrtc-extensions] Adding A/V-sync and one-way delay related data to RTCRtpContributingSource (#29)
- Re: [webrtc-extensions] Adding A/V-sync and one-way delay related data to RTCRtpContributingSource (#29)
- Re: [webrtc-extensions] Adding A/V-sync and one-way delay related data to RTCRtpContributingSource (#29)
[mediacapture-screen-share] Should fire ended track event when shared window/tab is closed. (#136)
[webrtc-pc] Pull Request: Chapter 8 testing: Mark what needs or doesn't need testing
[webrtc-pc] Pull Request: Test coverage review of Chapter 4.
[webrtc-pc] Pull Request: Annotating section 5
Re: [webrtc-pc] Review test coverage of the entire document (#2442)
[webrtc-pc] Pull Request: Check signalingState in queued task before firing ONN.
[webrtc-pc] Don't fire negotiationneeded outside of stable (#2471)
Re: [webrtc-stats] RTCInboundRtpStreamStats.estimatedEndToEndDelay (#538)
[webrtc-priority] new commits pushed by alvestrand
[webrtc-priority] new commits pushed by alvestrand
[webrtc-priority] new commits pushed by alvestrand
[webrtc-priority] new commits pushed by alvestrand
[webrtc-extensions] Allow more control over playoutDelay behavior (#28)
[webrtc-extensions] Allow more control over playoutDelay behaviuour (#27)
Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
- Re: [webrtc-stats] End-to-end delay metrics (#537)
[webrtc-extensions] RTCIceCredentialType has some formatting problem (#26)
[mediacapture-record] mimeType ambiguity: "video/webm;codecs=vp8" means? (#194)
- Re: [mediacapture-record] mimeType ambiguity: "video/webm;codecs=vp8" means? (#194)
- Re: [mediacapture-record] mimeType ambiguity: "video/webm;codecs=vp8" means? (#194)
- Re: [mediacapture-record] mimeType ambiguity: "video/webm;codecs=vp8" means? (#194)
- Re: [mediacapture-record] mimeType ambiguity: "video/webm;codecs=vp8" means? (#194)
[webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
- Re: [webrtc-stats] Define reception time for jitterBufferDelay stat (#549)
Re: [webrtc-extensions] Add promised based getDecoderCapabilities and getEncoderCapabilities (#23)
[webrtc-extensions] new commits pushed by henbos
Closed: [webrtc-extensions] Specify upper limit to playoutDelayHint (#11)
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] Test coverage chapter 5 (#2470)
[webrtc-pc] Test coverage chapter 11 (#2469)
[webrtc-pc] Test coverage chapter 9 (#2468)
[webrtc-pc] Test coverage chapter 4 (#2467)
[webrtc-pc] Test coverage chapter 8: Statistics model (#2466)
Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
- Re: [webrtc-extensions] Add RTP header negotiation control. (#25)
[webrtc-stats] Expose SCTP stats in RTCSctpTransportStats (#548)
- Re: [webrtc-stats] Expose SCTP stats in RTCSctpTransportStats (#548)
- Re: [webrtc-stats] Expose SCTP stats in RTCSctpTransportStats (#548)
[webrtc-pc] disallow pairing ice-tcp candidates with local ip addresses (#2465)
- Re: [webrtc-pc] disallow pairing ice-tcp candidates with local ip addresses (#2465)
- Re: [webrtc-pc] disallow pairing ice-tcp candidates with local ip addresses (#2465)
- Re: [webrtc-pc] disallow pairing ice-tcp candidates with local ip addresses (#2465)
[webrtc-pc] Test coverage chapter 7 (#2464)
[webrtc-pc] Test coverage chapter 6 (#2463)
[webrtc-stats] new commits pushed by vr000m
[webrtc-stats] new commits pushed by vr000m
[webrtc-stats] new commits pushed by vr000m
[webrtc-stats] new commits pushed by vr000m
[webrtc-stats] new commits pushed by vr000m
[webrtc-pc] Unit of RTCRtpEncodingParameters::maxBitrate is only implicitly defined (#2462)
- Re: [webrtc-pc] Unit of RTCRtpEncodingParameters::maxBitrate is only implicitly defined (#2462)
- Re: [webrtc-pc] Unit of RTCRtpEncodingParameters::maxBitrate is only implicitly defined (#2462)
[webrtc-pc] Pull Request: pc.close() does not fire connectionstatechange either
- Re: [webrtc-pc] pc.close() does not fire connectionstatechange either (#2461)
- Re: [webrtc-pc] pc.close() does not fire connectionstatechange either (#2461)
- Re: [webrtc-pc] pc.close() does not fire connectionstatechange either (#2461)
- Re: [webrtc-pc] pc.close() does not fire connectionstatechange either (#2461)
Re: [webrtc-svc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#22)
[mediacapture-record] Pull Request: Set default to optional dictionary
[webrtc-charter] Pull Request: Add Webrtc ICE as deliverable
Closed: [mediacapture-screen-share] What is the format of device ids? (#133)
[mediacapture-record] new commits pushed by jan-ivar
[webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
- Re: [webrtc-pc] `getCapabilities` seems to leak hardware capabilities w/o a permission (#2460)
[webrtc-stats] Pull Request: Fix a few IDL inconsistencies
- Re: [webrtc-stats] Fix a few IDL inconsistencies (#547)
- Re: [webrtc-stats] Fix a few IDL inconsistencies (#547)
[webrtc-stats] Pull Request: Mark some stats as only 'present' rather than 'valid' for some type o…
[webrtc-stats] Pull Request: Factor out definition of audio sample
- Re: [webrtc-stats] Factor out definition of audio sample (#545)
- Re: [webrtc-stats] Factor out definition of audio sample (#545)
[webrtc-stats] Pull Request: Use ReSpec auto-links
[webrtc-pc] https://www.w3.org/TR/2019/CR-webrtc-20191213/ (#2459)
[webrtc-stats] Pull Request: Remove CSS WebIDL prefix
[webrtc-pc] RTCAudioReceiverStats and RTCAudioSenderStats aren't MTI (#2458)
- Re: [webrtc-pc] RTCAudioReceiverStats and RTCAudioSenderStats aren't MTI (#2458)
- Re: [webrtc-pc] RTCAudioReceiverStats and RTCAudioSenderStats aren't MTI (#2458)
- Re: [webrtc-pc] RTCAudioReceiverStats and RTCAudioSenderStats aren't MTI (#2458)
- Re: [webrtc-pc] RTCAudioReceiverStats and RTCAudioSenderStats aren't MTI (#2458)
- Re: [webrtc-pc] RTCAudioReceiverStats and RTCAudioSenderStats aren't MTI (#2458)
[webrtc-stats] RTCRtpTransceiverStats doesn't inherit from RTCStats (#542)
[webrtc-pc] RTCIceCandidatePairStats.priority is listed as MTI but is obsolete (#2457)
[webrtc-stats] RTCDataChannelStats.dataChannelIdentifier should be unsigned short (#541)
[webrtc-stats] RTCVideoSourceStats.framesPerSecond should be a double (#540)
[webrtc-stats] Stats objects creation and WebRTC objects lifecycle (#539)
- Re: [webrtc-stats] Stats objects creation and WebRTC objects lifecycle (#539)
- Re: [webrtc-stats] Stats objects creation and WebRTC objects lifecycle (#539)
[webrtc-pc] Unclear result of stats filtering by sender/receiver. (#2456)
- Re: [webrtc-pc] Unclear result of stats filtering by sender/receiver. (#2456)
- Re: [webrtc-pc] Unclear result of stats filtering by sender/receiver. (#2456)
- Re: [webrtc-pc] Unclear result of stats filtering by sender/receiver. (#2456)
- Re: [webrtc-pc] Unclear result of stats filtering by sender/receiver. (#2456)