public-webrtc-logs@w3.org from May 2018 by subject

[webrtc-pc] Add internal slots for descriptions.

[webrtc-pc] Add support for WebRTC Data Channel in Workers

[webrtc-pc] Allow to import existing certificate

[webrtc-pc] Codify refusing to generate an empty Offer

[webrtc-pc] Data channel closing procedure

[webrtc-pc] Data channel minimum amount of streams supported

[webrtc-pc] Does direction matter for rejected m= sections?

[webrtc-pc] Does RTCStatsReport need a toJSON method?

[webrtc-pc] Editorial: Does throwing an error imply aborting the steps?

[webrtc-pc] editorial: remove getParameters/setParameters ()

[webrtc-pc] Fire events in SLD(answer) in direction rejection edge-case.

[webrtc-pc] Fix simulcast example

[webrtc-pc] Handling of invalid values in RTCRtpSender.setParameters()

[webrtc-pc] In-band negotiated channel should be open when dispatching

[webrtc-pc] Initial data channel state is inconsistent

[webrtc-pc] Invalidate [[LastReturnedParameters]] in RTCRtpSender.setParameters

[webrtc-pc] localDescription, remoteDescription et al. need internal slots

[webrtc-pc] new commits pushed by aboba

[webrtc-pc] new commits pushed by alvestrand

[webrtc-pc] new commits pushed by burnburn

[webrtc-pc] new commits pushed by stefhak

[webrtc-pc] new commits pushed by taylor-b

[webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?

[webrtc-pc] Pull Request: Add internal slots for descriptions.

[webrtc-pc] Pull Request: Correction for feature at risk

[webrtc-pc] Pull Request: editorial: remove getParameters/setParameters ()

[webrtc-pc] Pull Request: Fire events in SLD(answer) in direction rejection edge-case.

[webrtc-pc] Pull Request: Fix Respec link error

[webrtc-pc] Pull Request: Fix simulcast example

[webrtc-pc] Pull Request: Fix typo s/sdpCauseCode/sctpCauseCode/

[webrtc-pc] Pull Request: Improve replaceTrack prose; restores lost pre-negotiation behavior.

[webrtc-pc] Pull Request: Invalidate [[LastReturnedParameters]] in RTCRtpSender.setParameters

[webrtc-pc] Pull Request: Legacy methods do not throw exceptions.

[webrtc-pc] Pull Request: Make RTCCertificate unusable by other origins

[webrtc-pc] Pull Request: Make RTCSctpTransport.maxChannels nullable & line breaks

[webrtc-pc] Pull Request: Mark simulcast reception as a feature at risk

[webrtc-pc] Pull Request: receiver.getParameters clarification

[webrtc-pc] Pull Request: Require some codec dictionary members

[webrtc-pc] Pull Request: Specify that "throw" aborts processing

[webrtc-pc] Pull Request: Trim [[SendEncodings]] down to what user agent supports.

[webrtc-pc] Require some codec dictionary members

[webrtc-pc] RTCDataChannelInit unknown member handling

[webrtc-pc] RTCRtpDecodingParameters

[webrtc-pc] RTCSctpTransportState "new" never used

[webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities

[webrtc-pc] Should a signalingstatechange event be fired when closing a RTCPeerConnection?

[webrtc-pc] Spec-compliant way to get remote streams and tracks?

[webrtc-pc] Treat rejected m= sections (port of 0) as having "inactive" direction.

[webrtc-pc] Trim [[SendEncodings]] down to what user agent supports.

[webrtc-pc] Update structured cloning for recent changes to HTML

[webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?

[webrtc-pc] What should receiver.getParameters() return?

[webrtc-pc] What should sender.getParameters().codecs return before negotiation?

[webrtc-stats] Add a "panel test" to track implementation status

[webrtc-stats] add a graph showing the relationship of stats to the spec

[webrtc-stats] Add per layer stats for SVC

[webrtc-stats] Add stat for inputAudioLevel, before the audio filter

[webrtc-stats] Add stat for RTTs between client and STUN/TURN server

[webrtc-stats] Add stat to reflect the redundancy of FEC/RED data

[webrtc-stats] Clarify stats hierarchies

[webrtc-stats] Consider the Reporting API as a stats export mechanism

[webrtc-stats] Identifier ambiguity in stat objects

[webrtc-stats] new commits pushed by alvestrand

[webrtc-stats] new commits pushed by vr000m

[webrtc-stats] Pull Request: Define creation time for RTP objects

[webrtc-stats] Pull Request: Fixing some descriptions of ID references between stats objects.

[webrtc-stats] Should WebRTC be [SecureContext]

[webrtc-stats] Work through implications of simulcast on the receiver side

[webrtc-stats] Write a "how to add more stats" guideline document

Closed: [webrtc-pc] Data channel minimum amount of streams supported

Closed: [webrtc-pc] Data channel receive procedure missing?

Closed: [webrtc-pc] Does RTCStatsReport need a toJSON method?

Closed: [webrtc-pc] Editorial: Does throwing an error imply aborting the steps?

Closed: [webrtc-pc] Initial data channel state is inconsistent

Closed: [webrtc-pc] localDescription, remoteDescription et al. need internal slots

Closed: [webrtc-pc] No way to add track with stream associations to a given transceiver

Closed: [webrtc-pc] Not possible to tell how old `RTCRtpContributingSource.timestamp` is

Closed: [webrtc-pc] Recycling an m= section may not remove the old transceiver's remote track from its stream

Closed: [webrtc-pc] replaceTrack algorithm lost some important text

Closed: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition

Closed: [webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities

Closed: [webrtc-pc] Should a signalingstatechange event be fired when closing a RTCPeerConnection?

Closed: [webrtc-pc] should RTCRtpSender.setParameters invalidate LastReturnedParameters?

Closed: [webrtc-pc] Simulcast makes no sense for audio.

Closed: [webrtc-pc] Spec-compliant way to get remote streams and tracks?

Closed: [webrtc-stats] Add per layer stats for SVC

Closed: [webrtc-stats] Consider the Reporting API as a stats export mechanism

Closed: [webrtc-stats] Identifier ambiguity in stat objects

Closed: [webrtc-stats] Lifetime of RTPStreamStats

Closed: [webrtc-stats] Should WebRTC be [SecureContext]

Closed: [webrtc-stats] Unable to distinguish "sender" stats if multiple senders are sending the same track

Last message date: Thursday, 31 May 2018 21:11:38 UTC