Friday, 31 August 2018
- Closed: [webrtc-pc] Move [[WEBRTC-IDENTITY]] to its own repo
- [webrtc-pc] new commits pushed by dontcallmedom
- [webrtc-pc] new commits pushed by dontcallmedom
- Re: [webrtc-pc] Isolated Media Streams requires modification on permission algorithms in GUM and Permissions specs
- Re: [webrtc-pc] how to use datachannel bufferedamountlow threshold callback?
- Re: [webrtc-pc] Properly define origin (and handling thereof) for PeerConnection
- [webrtc-pc] how to use datachannel bufferedamountlow threshold callback?
- Re: [webrtc-pc] Is an RTCIceServer with no urls useful?
Thursday, 30 August 2018
- [webrtc-pc] Pull Request: Have getSenders()/getReceivers() return only non-stopped ones.
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] Reference to stalled IETF draft in 4.2.2
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] pc.getSenders() and getReceivers() include stopped ones.
- Re: [webrtc-pc] Isolated Media Streams requires modification on permission algorithms in GUM and Permissions specs
- Re: [webrtc-pc] Isolated Media Streams requires modification on permission algorithms in GUM and Permissions specs
- Re: [webrtc-pc] Remove identiyt from this repository
- [webrtc-pc] Pull Request: Remove identiyt from this repository
- Closed: [webrtc-pc] Ambiguous definition for IdP errors
- Closed: [webrtc-pc] Instantiating an IdP Proxy should be defined in terms of Fetch
- Closed: [webrtc-pc] Identity needs to refer to track not stream
- Closed: [webrtc-pc] RTCError suberrors for identity should move to identity spec
- Closed: [webrtc-pc] Isolated Media Streams requires modification on permission algorithms in GUM and Permissions specs
- Closed: [webrtc-pc] RTCIdentityProviderGlobalScope looks wrong
- Closed: [webrtc-pc] getIdentityAssertion should reject with InvalidAccessError if no identity provider is set
- Closed: [webrtc-pc] How is port number specified when verifying peer identity's assertion?
- Closed: [webrtc-pc] Origin value for IdP proxy script
- Closed: [webrtc-pc] Specifying third party IdP for validating assertion
- Closed: [webrtc-pc] Section 10.4.1: target peerIdentity
- Closed: [webrtc-pc] Format of provider string for setIdentityProvider and validation
- Closed: [webrtc-pc] `addTransceiver(track)` doesn't mention checking the origin of track
- Closed: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Closed: [webrtc-pc] Section 9.1: when is IdP ready?
- Closed: [webrtc-pc] Section 9.4: peerIdentity mismatches
- Closed: [webrtc-pc] Clarity in section 9.7 example 11
- Closed: [webrtc-pc] Lifetime of pc.PeerIdentity
- Re: [webrtc-pc] Is an RTCIceServer with no urls useful?
- Re: [webrtc-pc] pc.getSenders() and getReceivers() include stopped ones.
- Re: [webrtc-pc] pc.getSenders() and getReceivers() include stopped ones.
Wednesday, 29 August 2018
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] pc.getSenders() and getReceivers() include stopped ones.
- [webrtc-pc] pc.getSenders() and getReceivers() include stopped ones.
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
Tuesday, 28 August 2018
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] Sort out meaning of "Fire event with OperationError exception"
- Re: [webrtc-pc] RTCDataChannel.bufferedAmountLowThreshold not handled correctly
- Re: [webrtc-pc] RTCDataChannel.bufferedAmountLowThreshold not handled correctly
- [webrtc-pc] RTCDataChannel.bufferedAmountLowThreshold not handled correctly
Monday, 27 August 2018
- Re: [webrtc-pc] Reference to stalled IETF draft in 4.2.2
- Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
- Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- [webrtc-pc] Reference to stalled IETF draft in 4.2.2
- Re: [webrtc-pc] Make possible to select TURN allocataion address familly. (to avoid IPv6 confusion)
- Closed: [webrtc-pc] Error for when peer identity is wrong
- Re: [webrtc-pc] Error for when peer identity is wrong
- Re: [webrtc-pc] Handing SDP with more than one identity
- Closed: [webrtc-pc] Handing SDP with more than one identity
- [webrtc-pc] Make possible to select TURN allocataion address familly. (to avoid IPv6 confusion)
- Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- Closed: [webrtc-pc] Be consistent when rejecting with an OperationError
- Re: [webrtc-pc] Be consistent when rejecting with an OperationError
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- Re: [webrtc-pc] Added error detail "datachannel-id-generation-error", using in error …
- [webrtc-pc] Pull Request: Added error detail "datachannel-id-generation-error", using in error …
Sunday, 26 August 2018
Friday, 24 August 2018
Thursday, 23 August 2018
- Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] Sort out meaning of "Fire event with OperationError exception"
- Re: [webrtc-pc] A shot at aligning eventfiring with how it's specified in other docs.
Wednesday, 22 August 2018
- Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
- Re: [webrtc-pc] WebRTC bypass CSP connect-src policies
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
- [webrtc-pc] Properly define origin (and handling thereof) for PeerConnection
- Re: [webrtc-pc] A shot at aligning eventfiring with how it's specified in other docs.
- Re: [webrtc-stats] RTCIceCandidateType: is it 'relay' or 'relayed'
Tuesday, 21 August 2018
- Re: [webrtc-stats] RTCIceCandidateType: is it 'relay' or 'relayed'
- Re: [webrtc-pc] A shot at aligning eventfiring with how it's specced in other docs.
- [webrtc-stats] RTCIceCandidateType: is it 'relay' or 'relayed'
Monday, 20 August 2018
- Re: [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
- Re: [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
- Closed: [webrtc-pc] Inconsistencies in Asynchronous Task Queueing
- Re: [webrtc-pc] Inconsistencies in Asynchronous Task Queueing
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] A shot at aligning eventfiring with how it's specced in other docs.
- [webrtc-pc] Pull Request: Align rejection with OperationError.
- [webrtc-pc] Be consistent when rejecting with an OperationError
- [webrtc-pc] Pull Request: A shot at aligning eventfiring with how it's specced in other docs.
Thursday, 16 August 2018
- Closed: [webrtc-pc] Use automatically generated default toJSON() method (when available)
- Re: [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
- Re: [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
- Re: [webrtc-pc] Events not bubbling
- Closed: [webrtc-pc] Gatherer state vs gathering state
- Closed: [webrtc-pc] Failed to execute 'insertDTMF' on 'RTCDTMFSender': The 'canInsertDTMF' attribute is false: this sender cannot send DTMF.
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
- [webrtc-pc] Describe consistency model between *{local|remote}*Description attributes
Wednesday, 15 August 2018
- Re: [webrtc-pc] Effect of RTCRtpSendParameters on Simulcast
- Re: [webrtc-pc] Effect of RTCRtpSendParameters on Simulcast
Tuesday, 14 August 2018
- [webrtc-pc] Effect of RTCRtpSendParameters on Simulcast
- Re: [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described
- Re: [webrtc-pc] Remove simulcast material and refer to simulcast draft
- Re: [webrtc-pc] Move [[WEBRTC-IDENTITY]] to its own repo
- Re: [webrtc-pc] Move [[WEBRTC-IDENTITY]] to its own repo
- [webrtc-pc] Pull Request: Remove simulcast material and refer to simulcast draft
- Re: [webrtc-pc] Remove simulcast material and refer to simulcast draft
- Re: [webrtc-pc] Remove simulcast material and refer to simulcast draft
Monday, 13 August 2018
- [webrtc-pc] Pull Request: Remove simulcast material and refer to simulcast draft
- [webrtc-pc] Move Simulcast to Separate Document
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Events not bubbling
Sunday, 12 August 2018
Friday, 10 August 2018
- Re: [webrtc-pc] Gatherer state vs gathering state
- Re: [webrtc-pc] Failed to execute 'insertDTMF' on 'RTCDTMFSender': The 'canInsertDTMF' attribute is false: this sender cannot send DTMF.
- Re: [webrtc-pc] Gatherer state vs gathering state
- Re: [webrtc-pc] Gatherer state vs gathering state
- [webrtc-pc] Gatherer state vs gathering state
- Re: [webrtc-pc] Failed to execute 'insertDTMF' on 'RTCDTMFSender': The 'canInsertDTMF' attribute is false: this sender cannot send DTMF.
- [webrtc-pc] Failed to execute 'insertDTMF' on 'RTCDTMFSender': The 'canInsertDTMF' attribute is false: this sender cannot send DTMF.
Thursday, 9 August 2018
- Re: [webrtc-pc] Use automatically generated default toJSON() method (when available)
- Re: [webrtc-pc] Use automatically generated default toJSON() method (when available)
- Re: [webrtc-pc] Events not bubbling
- Closed: [webrtc-pc] Superfluous union in addIceCandidate.
- [webrtc-pc] new commits pushed by stefhak
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Remove superfluous union on addIceCandidate
- Re: [webrtc-pc] canInsertDTMF transitions not specified
- Re: [webrtc-pc] canInsertDTMF transitions
- [webrtc-pc] Pull Request: canInsertDTMF transitions
Tuesday, 7 August 2018
- Re: [webrtc-pc] Provide changelog for the spec in new editors draft workflow
- Closed: [webrtc-pc] Provide changelog for the spec in new editors draft workflow
- Re: [webrtc-pc] Use automatically generated default toJSON() method (when available)
- Re: [webrtc-pc] Superfluous union in addIceCandidate.
Monday, 6 August 2018
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] Superfluous union in addIceCandidate.
- [webrtc-pc] Pull Request: Make Section references more specific
- Re: [webrtc-pc] Superfluous union in addIceCandidate.
- Re: [webrtc-pc] Superfluous union in addIceCandidate.
- Re: [webrtc-stats] Fix inconsistent RTC{RTP,Rtp}StreamStats
Friday, 3 August 2018
- [webrtc-pc] Pull Request: Remove superfluous union on addIceCandidate
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- [webrtc-pc] Superfluous union in addIceCandidate.
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- [webrtc-pc] Pull Request: Added checks to make sure maxFramerate is not negative.
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
Thursday, 2 August 2018
- Re: [webrtc-pc] don't abbrev setLocalDescription/setRemoteDescription
- Re: [webrtc-pc] don't abbrev setLocalDescription/setRemoteDescription
- [webrtc-pc] new commits pushed by jan-ivar
- Re: [webrtc-pc] don't abbrev setLocalDescription/setRemoteDescription
- Re: [webrtc-pc] Is an RTCIceServer with no urls useful?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Closed: [webrtc-pc] Does direction matter for rejected m= sections?
- Re: [webrtc-pc] Does direction matter for rejected m= sections?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] Is an RTCIceServer with no urls useful?
- Closed: [webrtc-pc] setLocal and setRemote wrong
- Re: [webrtc-pc] Made maxFramerate and scaleResolutionDownBy unsigned long (were: doub…
- Closed: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy is "require" and SDP is missing "a=rtcp-mux"
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Made maxFramerate and scaleResolutionDownBy unsigned long (were: doub…
- [webrtc-stats] Pull Request: Fix inconsistent RTC{RTP,Rtp}StreamStats
- Re: [webrtc-pc] Made maxFramerate and scaleResolutionDownBy unsigned long (were: doub…
- Re: [webrtc-pc] throw NotSupportedError when mux policy does not match
Wednesday, 1 August 2018
- Re: [webrtc-pc] Made maxFramerate and scaleResolutionDownBy unsigned long (were: doub…
- Re: [webrtc-pc] Handling of invalid values in RTCRtpSender.setParameters()
- Re: [webrtc-pc] How do I indicate the end of remote candidates?
- [webrtc-pc] How do I indicate the end of remote candidates?
- Re: [webrtc-pc] Is an RTCIceServer with no urls useful?
- Re: [webrtc-pc] setLocal and setRemote wrong
- [webrtc-pc] Pull Request: don't abbrev setLocalDescription/setRemoteDescription
- Re: [webrtc-pc] setLocal and setRemote wrong
- Re: [webrtc-pc] setLocal and setRemote wrong
- Re: [webrtc-pc] Is an RTCIceServer with no urls useful?
- [webrtc-stats] identifying the ice generation of a candidate pair
- [webrtc-pc] setLocal and setRemote wrong