Re: [webrtc-pc] Add support for WebRTC Data Channel in Workers
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: createDataChannel: Queue a task to update negotiation needed state
Re: [webrtc-stats] RTCMediaStreamTrackStats.jitterBufferDelay: Specify unit in seconds
[webrtc-stats] new commits pushed by vr000m
Re: [webrtc-stats] RTCMediaStreamTrackStats.concealedAudibleSamples added.
[webrtc-stats] pliCount is Picture Loss Indication, not Packet Loss Indication
- Re: [webrtc-stats] pliCount is Picture Loss Indication, not Packet Loss Indication
- Closed: [webrtc-stats] pliCount is Picture Loss Indication, not Packet Loss Indication
- Re: [webrtc-stats] pliCount is Picture Loss Indication, not Packet Loss Indication
[webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
- Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples
[webrtc-pc] Stats & isolated streams
[webrtc-stats] CPU metrics
- Re: [webrtc-stats] CPU metrics
- Re: [webrtc-stats] CPU metrics
- Re: [webrtc-stats] CPU metrics
- Re: [webrtc-stats] CPU metrics
- Re: [webrtc-stats] CPU metrics
- Re: [webrtc-stats] CPU metrics
Re: [webrtc-stats] Privacy & Security self review
[webrtc-pc] No way to tell when SCTP association is closed
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: Fix a typo: RTCSessionSessionDescription -> RTCSessionDescription.
[webrtc-pc] Pull Request: Improve definition of required fields in RTCRtpParameters
Re: [webrtc-stats] Typo fix datachannelid to datachannelId
[webrtc-pc] Partial removal of a track?
- Re: [webrtc-pc] Partial removal of a track?
- Re: [webrtc-pc] Partial removal of a track?
- Re: [webrtc-pc] Partial removal of a track?
[webrtc-pc] Pull Request: Validate protocol string in IdP operations
Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
[webrtc-pc] Pull Request: DTMF examples
[webrtc-pc] DTMF examples
[webrtc-pc] Message text not localizable
- Re: [webrtc-pc] Message text not localizable
- Closed: [webrtc-pc] Message text not localizable
- Re: [webrtc-pc] Message text not localizable
[webrtc-pc] Pull Request: Add 'resolved' (and variants) to Promise terminology
[webrtc-pc] Promise terminology is missing "resolved"
Re: [webrtc-pc] setParameters: Do argument checks in sync section and specify parellel steps
[webrtc-pc] RTCRtpSender.setParameters: Do we need more specific hardware encoder errors?
[webrtc-pc] RTCDtlsTransportState enum descriptions are lacking
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by burnburn
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by burnburn
Closed: [webrtc-pc] Setting a remote description may cause discontinuity due to codec switching.
[webrtc-pc] new commits pushed by burnburn
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] editorial: update the ice gathering state: firing icecandidate with null is a legacy hack
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] editorial: 4.3.1 Operation "settled" is not defined
[webrtc-pc] new commits pushed by burnburn
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: RTCIceTransport.gatheringState: Fix type inconsistency
Re: [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
[webrtc-pc] Ordering of stream "addtrack"/"removetrack" events vs. "track" event
Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
[webrtc-pc] Pull Request: Revert "Adding `remoteTrackId` attribute to represent SDP-signaled track ID."
Closed: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
Closed: [webrtc-pc] Do we need a "trackremoved" event?
[webrtc-pc] createDataChannel touches DOM "in the background"
Re: [webrtc-pc] Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set
Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
Re: [webrtc-pc] Remove event.receiver.
Re: [webrtc-pc] What algorithms the browser supports
Re: [webrtc-pc] Section 5.3: track.label initialization
[webrtc-pc] Pull Request: Add Promise terms to Terminology section
Re: [webrtc-stats] Need DSCP information for outgoing RTP streams
[webrtc-pc] Pull Request: Add note that null candidate is for legacy compatibility
[webrtc-pc] RTCIceTransport.gatheringState: Mismatching types between IDL and description
- Re: [webrtc-pc] RTCIceTransport.gatheringState: Mismatching types between IDL and description
- Closed: [webrtc-pc] RTCIceTransport.gatheringState: Mismatching types between IDL and description
[webrtc-stats] Pull Request: Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
- Re: [webrtc-stats] Added Guidelines for getStats() results caching
Closed: [webrtc-stats] Need implementation advice on caching
Re: [webrtc-stats] Need implementation advice on caching
Re: [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
- Re: [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
- Re: [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
- Re: [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
Re: [webrtc-stats] RTCMediaStreamTrackStats.concealedAudibleSamples
[webrtc-stats] Pull Request: keyFramesSent and keyFramesReceived added
[webrtc-pc] Pull Request: connectionstate: add missing "one"
[webrtc-stats] Is bytesReceived really available for RTCRemoteInboundRTPStreamStats?
- Re: [webrtc-stats] Is bytesReceived really available for RTCRemoteInboundRTPStreamStats?
- Re: [webrtc-stats] Is bytesReceived really available for RTCRemoteInboundRTPStreamStats?
- Re: [webrtc-stats] Is bytesReceived really available for RTCRemoteInboundRTPStreamStats?
[webrtc-pc] new commits pushed by taylor-b
Closed: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
Re: [webrtc-pc] Ensure that "track" events fire before the SRD promise resolves.
[webrtc-pc] Pull Request: Select sent codec via "codecPayloadType" field rather than reordering.
- Re: [webrtc-pc] Select sent codec via "codecPayloadType" field rather than reordering.
- Re: [webrtc-pc] Select sent codec via "codecPayloadType" field rather than reordering.
- Re: [webrtc-pc] Select sent codec via "codecPayloadType" field rather than reordering.
[webrtc-pc] Pull Request: Add some text about how the [[AssociatedMediaStreams]] slot is used
Re: [webrtc-pc] [[associated MediaStreams]] internal slot for RTCRtpSender is not used
[webrtc-pc] Pull Request: Use internal slots for transceiver's sender/receiver and receiver's track
[webrtc-pc] RTCRtpTransceiver should have internal slots for its sender and receiver
[webrtc-pc] Clarify (if needed) how remoteTrackId relates to MSID in the SDP
[webrtc-pc] Pull Request: s/RTCTransceiver/RTCRtpTransceiver
[webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
- Re: [webrtc-pc] behaviour of offerToReceive* set to false when there is a local track
[webrtc-pc] Pull Request: Use internal slot for RTCRtpSender's track
[webrtc-pc] RTCRtpReceiver should have an internal slot for its track
[webrtc-pc] RTCRtpSender should have an internal slot for its track
[webrtc-pc] Pull Request: RTCIceTransport: Use internal slots
[webrtc-pc] Pull Request: RTCDtlsTransport: Use internal slots
Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
Re: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
- Re: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
- Re: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
[webrtc-stats] Stats for Audio network adaptation
- Re: [webrtc-stats] Stats for Audio network adaptation
- Re: [webrtc-stats] Stats for Audio network adaptation
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] "Firing an RTCTrackEvent event named e" is never referenced
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: Fixed UA -> user agent.
[webrtc-pc] Pull Request: Fixed spelling of scaleResolutionDownBy in example.
[webrtc-pc] Pull Request: Patch for #1564.
- Re: [webrtc-pc] scaleResolutionDownBy: Specify how the User Agent should behave when scaling video
- Re: [webrtc-pc] scaleResolutionDownBy: Specify how the User Agent should behave when scaling video
[webrtc-pc] Pull Request: Editorial: Link to 'Firing a something event' definitions
Re: [webrtc-pc] "Firing an RTCTrackEvent event named e" is never referenced
[webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture
- Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture
- Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture
- Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture
- Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture
Re: [webrtc-pc] Section 5.2: centering, scaling, cropping
[webrtc-pc] state internal slot
Re: [webrtc-pc] Annotate all interfaces with Exposed extended attribute
[webrtc-pc] Add [Exposed] to all interfaces
[webrtc-pc] Pull Request: Editorial: Remove unreferenced [HTML] ref using respec post processing
Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
[webrtc-pc] Pull Request: First shot at patch for Issue #1283.
- Re: [webrtc-pc] First shot at patch for Issue #1283.
- Re: [webrtc-pc] Resizing video (fix for Issue 1283)
- Re: [webrtc-pc] Resizing video (fix for Issue 1283)
- Re: [webrtc-pc] Resizing video (fix for Issue 1283)
- Re: [webrtc-pc] Resizing video (fix for Issue 1283)
- Re: [webrtc-pc] Resizing video (fix for Issue 1283)
Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
Re: [webrtc-pc] Adding `remoteTrackId` attribute to represent SDP-signaled track ID.
[webrtc-pc] Setting local/remote descriptions in succession without waiting for the promises to resolve
- Re: [webrtc-pc] Setting local/remote descriptions in succession without waiting for the promises to resolve
- Closed: [webrtc-pc] Setting local/remote descriptions in succession without waiting for the promises to resolve
- Re: [webrtc-pc] Setting local/remote descriptions in succession without waiting for the promises to resolve