- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 02 Oct 2018 17:00:47 +0000
- To: public-webrtc@w3.org
- Message-Id: <E1g7O2R-0008OX-Tf@uranus.w3.org>
Issues
------
* w3c/webrtc-pc (+5/-3/💬8)
5 issues created:
- Should RTCRtpTransceiver.setCodecPreferences() only refer to RTCRtpReceiver.getCapabilities(kind)? (by Orphis)
https://github.com/w3c/webrtc-pc/issues/1998
- DTMF scheduling is subject to JS queueng delays (by alvestrand)
https://github.com/w3c/webrtc-pc/issues/1997
- Possible race between unmuting a remote track and setRemoteDescription() muting it. (by henbos)
https://github.com/w3c/webrtc-pc/issues/1994
- setRemoteDescription() adding and removing tracks to streams should be synchronous (by henbos)
https://github.com/w3c/webrtc-pc/issues/1993
- Define what happens if maxFramerate is 0? (by stefhak)
https://github.com/w3c/webrtc-pc/issues/1992
6 issues received 8 new comments:
- #1983 getSynchronizationSources (and getContriburingSources) should work for video too (3 by jan-ivar, na-g)
https://github.com/w3c/webrtc-pc/issues/1983 [PR exists] [September 2018 interim]
- #1992 Define what happens if maxFramerate is 0? (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/1992
- #1994 Possible race between unmuting a remote track and setRemoteDescription() muting it. (1 by henbos)
https://github.com/w3c/webrtc-pc/issues/1994
- #1964 Effect of RTCRtpSendParameters on Simulcast (1 by aboba)
https://github.com/w3c/webrtc-pc/issues/1964 [Simulcast]
- #1973 Reference to stalled IETF draft in 4.2.2 (1 by stefhak)
https://github.com/w3c/webrtc-pc/issues/1973 [Editorial] [Ready for PR]
- #1834 Handling of invalid values in RTCRtpSender.setParameters() (1 by stefhak)
https://github.com/w3c/webrtc-pc/issues/1834 [PR exists]
3 issues closed:
- Possible race between unmuting a remote track and setRemoteDescription() muting it. https://github.com/w3c/webrtc-pc/issues/1994
- setRemoteDescription() adding and removing tracks to streams should be synchronous https://github.com/w3c/webrtc-pc/issues/1993
- Reference to stalled IETF draft in 4.2.2 https://github.com/w3c/webrtc-pc/issues/1973 [Editorial] [Ready for PR]
* w3c/webrtc-stats (+2/-0/💬6)
2 issues created:
- Is exposing a remote peer IP address through RTCIceCandidateStats.address a privacy issue (by youennf)
https://github.com/w3c/webrtc-stats/issues/375
- Exposing RTCIceCandidateStats.networkType might trigger fingerprinting (by youennf)
https://github.com/w3c/webrtc-stats/issues/374
2 issues received 6 new comments:
- #374 Exposing RTCIceCandidateStats.networkType might trigger fingerprinting (4 by vr000m, youennf)
https://github.com/w3c/webrtc-stats/issues/374
- #375 Is exposing a remote peer IP address through RTCIceCandidateStats.address a privacy issue (2 by vr000m, youennf)
https://github.com/w3c/webrtc-stats/issues/375
* w3c/webrtc-quic (+6/-4/💬14)
6 issues created:
- API change - solving state & unidirectional streams (by shampson)
https://github.com/w3c/webrtc-quic/issues/69
- Security and client -> server use cases without ICE (by pthatcherg)
https://github.com/w3c/webrtc-quic/issues/67
- Stats, there got to be stats... (by vr000m)
https://github.com/w3c/webrtc-quic/issues/66
- RTCQuicStream state (by shampson)
https://github.com/w3c/webrtc-quic/issues/65 [question]
- Access to [[Readable]] and [[Writable]] (by shampson)
https://github.com/w3c/webrtc-quic/issues/64 [question]
- Cleaning up read API (by shampson)
https://github.com/w3c/webrtc-quic/issues/63
8 issues received 14 new comments:
- #69 API change - solving state & unidirectional streams (5 by shampson, aboba)
https://github.com/w3c/webrtc-quic/issues/69 [question]
- #65 RTCQuicStream state (2 by pthatcherg, shampson)
https://github.com/w3c/webrtc-quic/issues/65
- #66 Stats, there got to be stats... (2 by steveanton, vr000m)
https://github.com/w3c/webrtc-quic/issues/66
- #42 RTCQuicTransport: multiple events fire with QUIC error (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/42 [Ready for PR] [question]
- #55 createStream() triggering remote stream creation (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/55 [question]
- #56 Synchronous Events Firing (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/56
- #62 Expose error code and reason for stop() and reset()? (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/62 [question]
- #63 Cleaning up read API (1 by pthatcherg)
https://github.com/w3c/webrtc-quic/issues/63
4 issues closed:
- Purpose of targetWriteBufferedAmount https://github.com/w3c/webrtc-quic/issues/16 [PR exists]
- Clarification on buffering https://github.com/w3c/webrtc-quic/issues/21 [PR exists]
- More details for stop() https://github.com/w3c/webrtc-quic/issues/37 [PR exists]
- Uni-directional stream support https://github.com/w3c/webrtc-quic/issues/44 [PR exists]
* w3c/webrtc-nv-use-cases (+0/-0/💬1)
1 issues received 1 new comments:
- #1 IoT use-case requires direct one-way media support (1 by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/1
* w3c/mediacapture-main (+0/-0/💬10)
1 issues received 10 new comments:
- #541 enumerateDevices() doesn't mention how to handle OS device permissions (10 by dontcallmedom, jan-ivar, guidou, alvestrand, youennf)
https://github.com/w3c/mediacapture-main/issues/541
* w3c/mediacapture-output (+2/-3/💬6)
2 issues created:
- setSinkId is inconsistent in handling of default value. (by jan-ivar)
https://github.com/w3c/mediacapture-output/issues/79
- Should setSinkId be functional in SecureContext only? (by jan-ivar)
https://github.com/w3c/mediacapture-output/issues/78
4 issues received 6 new comments:
- #77 It is unclear why https://w3c.github.io/mediacapture-output/#dom-htmlmediaelement-setsinkid 5.5 needs to queue a task (2 by guidou)
https://github.com/w3c/mediacapture-output/issues/77
- #71 Enumeration of output devices and permission model (2 by guidou)
https://github.com/w3c/mediacapture-output/issues/71 [question]
- #79 setSinkId is inconsistent in handling of default value. (1 by guidou)
https://github.com/w3c/mediacapture-output/issues/79
- #78 Should setSinkId be functional in SecureContext only? (1 by guidou)
https://github.com/w3c/mediacapture-output/issues/78
3 issues closed:
- It is unclear why https://w3c.github.io/mediacapture-output/#dom-htmlmediaelement-setsinkid 5.5 needs to queue a task https://github.com/w3c/mediacapture-output/issues/77
- Enumeration of output devices and permission model https://github.com/w3c/mediacapture-output/issues/71 [question]
- setSinkId is inconsistent in handling of default value. https://github.com/w3c/mediacapture-output/issues/79
* w3c/mediacapture-screen-share (+0/-1/💬3)
2 issues received 3 new comments:
- #62 Offer high level source filtering (2 by jan-ivar, niklasenbom)
https://github.com/w3c/mediacapture-screen-share/issues/62 [List Discussion Needed] [September 2018 Virtual Interim]
- #72 Describe what happens if the window is closed or the monitor is disconnected (1 by henbos)
https://github.com/w3c/mediacapture-screen-share/issues/72 [September 2018 Virtual Interim]
1 issues closed:
- MediaTrackConstraints usage contradiction https://github.com/w3c/mediacapture-screen-share/issues/67 [PR exists]
Pull requests
-------------
* w3c/webrtc-pc (+2/-0/💬2)
2 pull requests submitted:
- Simulcast behavior (by aboba)
https://github.com/w3c/webrtc-pc/pull/1996 [Simulcast]
- Move priority from RTCRtpEncodingParameters to RTCRtpSendParameters (by aboba)
https://github.com/w3c/webrtc-pc/pull/1995
2 pull requests received 2 new comments:
- #1986 getSynchronizationSources/getContributingSources for video as well (1 by henbos)
https://github.com/w3c/webrtc-pc/pull/1986
- #1946 Add warning to RTCRtpTransceiver.stop(). Stop rejected transceivers at SLD(). (1 by alvestrand)
https://github.com/w3c/webrtc-pc/pull/1946
* w3c/webrtc-quic (+1/-4/💬5)
1 pull requests submitted:
- Add support for uni-directional streams (by aboba)
https://github.com/w3c/webrtc-quic/pull/68
3 pull requests received 5 new comments:
- #58 Add support for uni-directional streams (3 by shampson, aboba)
https://github.com/w3c/webrtc-quic/pull/58
- #52 RTCQuicTransport.stop() closes streams. (1 by shampson)
https://github.com/w3c/webrtc-quic/pull/52
- #60 Redo target write buffer amount (1 by shampson)
https://github.com/w3c/webrtc-quic/pull/60
4 pull requests merged:
- Add support for uni-directional streams
https://github.com/w3c/webrtc-quic/pull/68
- Redo target write buffer amount
https://github.com/w3c/webrtc-quic/pull/60 [Editors can integrate]
- Remove target read buffered amount
https://github.com/w3c/webrtc-quic/pull/57 [Editors can integrate]
- RTCQuicTransport.stop() closes streams.
https://github.com/w3c/webrtc-quic/pull/52
* w3c/mediacapture-main (+0/-1/💬0)
1 pull requests merged:
- Have getCapabilities() return an empty dictionary instead of null
https://github.com/w3c/mediacapture-main/pull/539
* w3c/mediacapture-output (+1/-1/💬0)
1 pull requests submitted:
- Initialize [[SinkId]] to "". (by jan-ivar)
https://github.com/w3c/mediacapture-output/pull/80
1 pull requests merged:
- Initialize [[SinkId]] to "".
https://github.com/w3c/mediacapture-output/pull/80
* w3c/mediacapture-screen-share (+0/-1/💬1)
1 pull requests received 1 new comments:
- #75 Extend constraints to constrainable patterns (1 by jan-ivar)
https://github.com/w3c/mediacapture-screen-share/pull/75
1 pull requests merged:
- Extend constraints to constrainable patterns
https://github.com/w3c/mediacapture-screen-share/pull/75
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webrtc-pc
* https://github.com/w3c/webrtc-identity
* https://github.com/w3c/webrtc-stats
* https://github.com/w3c/webrtc-charter
* https://github.com/w3c/webrtc-dscp-exp
* https://github.com/w3c/webrtc-quic
* https://github.com/w3c/webrtc-ice
* https://github.com/w3c/webrtc-nv-use-cases
* https://github.com/w3c/mediacapture-main
* https://github.com/w3c/mediacapture-record
* https://github.com/w3c/mediacapture-image
* https://github.com/w3c/mediacapture-depth
* https://github.com/w3c/mediacapture-fromelement
* https://github.com/w3c/mediacapture-output
* https://github.com/w3c/mediacapture-screen-share
* https://github.com/w3c/mst-content-hint
Received on Tuesday, 2 October 2018 17:01:00 UTC