- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 20 Nov 2018 17:01:21 +0000
- To: public-webrtc@w3.org
- Message-Id: <E1gP9Or-0004Nf-Gf@uranus.w3.org>
Issues
------
* w3c/webrtc-pc (+2/-2/💬28)
2 issues created:
- RTCRtpReceiver.getParameters() clarification (by Orphis)
https://github.com/w3c/webrtc-pc/issues/2032
- Partially connected peerconnection might have "new" connectionstate. (by jonasesolsson)
https://github.com/w3c/webrtc-pc/issues/2031
13 issues received 28 new comments:
- #2023 Should we remove getDefaultIceServers? (12 by juberti, jan-ivar, misi, alvestrand)
https://github.com/w3c/webrtc-pc/issues/2023 [Needs Test] [Ready for PR]
- #2032 RTCRtpReceiver.getParameters() clarification (3 by Orphis, alvestrand, aboba)
https://github.com/w3c/webrtc-pc/issues/2032 [question]
- #2027 special-casing of a=msid:- (2 by fippo, alvestrand)
https://github.com/w3c/webrtc-pc/issues/2027
- #2008 Using codecPayloadType with addTransceiver() (2 by henbos, alvestrand)
https://github.com/w3c/webrtc-pc/issues/2008 [Ready for PR] [Simulcast] [TPAC 2018]
- #2019 Start using new issue labels (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2019
- #2024 Differences between pc.removeTrack(sender) and sender.replaceTrack(null) (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2024 [question]
- #2026 Should WPT webrtc folder be renamed to webrtc-pc (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2026
- #2028 setCodecPreferences and RTX / RED / FEC codecs (1 by henbos)
https://github.com/w3c/webrtc-pc/issues/2028 [Ready for PR]
- #1930 Rename sender.transport.transport to sender.transport.iceTransport? (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/1930 [PR exists] [TPAC 2018]
- #1940 transceiver.direction doesn’t respond, if out-of-sync. (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/1940 [Ready for PR] [TPAC 2018]
- #1974 RTCDataChannel.bufferedAmountLowThreshold not handled correctly (1 by lgrahl)
https://github.com/w3c/webrtc-pc/issues/1974
- #2011 Matching of origin for RTCCertificate objects is unclear (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2011
- #1981 RTCIceTransport selected candidate pair behavior when changing state (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/1981 [TPAC 2018]
2 issues closed:
- Rename sender.transport.transport to sender.transport.iceTransport? https://github.com/w3c/webrtc-pc/issues/1930 [PR exists] [TPAC 2018]
- special-casing of a=msid:- https://github.com/w3c/webrtc-pc/issues/2027
* w3c/webrtc-stats (+1/-0/💬3)
1 issues created:
- RTCPeerConnectionStats appear redundant. Remove? (by jan-ivar)
https://github.com/w3c/webrtc-stats/issues/382
1 issues received 3 new comments:
- #382 RTCPeerConnectionStats appear redundant. Remove? (3 by vr000m, jan-ivar, alvestrand)
https://github.com/w3c/webrtc-stats/issues/382
* w3c/webrtc-dscp-exp (+1/-0/💬0)
1 issues created:
- Security and Privacy Questionnaire (by alvestrand)
https://github.com/w3c/webrtc-dscp-exp/issues/3
* w3c/webrtc-quic (+2/-3/💬10)
2 issues created:
- Language for RTCIceTransport causing RTCQuicTransport to become closed (by steveanton)
https://github.com/w3c/webrtc-quic/issues/85
- Updating RTCQuicTransport onstatechange event to Promise (by shampson)
https://github.com/w3c/webrtc-quic/issues/83
7 issues received 10 new comments:
- #77 Adding support for DATAGRAM (2 by pthatcherg, aboba)
https://github.com/w3c/webrtc-quic/issues/77
- #79 Support for Transport parameters (2 by pthatcherg)
https://github.com/w3c/webrtc-quic/issues/79
- #55 createStream() triggering remote stream creation (2 by shampson)
https://github.com/w3c/webrtc-quic/issues/55 [Ready for PR]
- #81 Resolving multiple waitForWriteBufferedAmountBelow/waitForReadable promises (1 by steveanton)
https://github.com/w3c/webrtc-quic/issues/81
- #83 Updating RTCQuicTransport onstatechange event to Promise (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/83
- #62 Expose error code and reason for stop() and reset()? (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/62 [PR exists]
- #63 Cleaning up read API (1 by shampson)
https://github.com/w3c/webrtc-quic/issues/63
3 issues closed:
- Cleaning up read API https://github.com/w3c/webrtc-quic/issues/63
- Expose error code and reason for stop() and reset()? https://github.com/w3c/webrtc-quic/issues/62 [PR exists]
- Resolving multiple waitForWriteBufferedAmountBelow/waitForReadable promises https://github.com/w3c/webrtc-quic/issues/81
* w3c/mediacapture-main (+0/-2/💬7)
5 issues received 7 new comments:
- #551 Should we allow empty string device IDs? (3 by jan-ivar, alvestrand)
https://github.com/w3c/mediacapture-main/issues/551
- #553 should enumerateDevices list infrared cameras by default? (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/553
- #554 Specify a way for WebDriver to add/remove/setup capture devices (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/554
- #540 Should getUserMedia be functional in SecureContext only? (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/540 [TPAC 2018]
- #532 What does it mean to 'combine' origins? (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/532 [TPAC 2018]
2 issues closed:
- Should getUserMedia be functional in SecureContext only? https://github.com/w3c/mediacapture-main/issues/540 [TPAC 2018]
- What does it mean to 'combine' origins? https://github.com/w3c/mediacapture-main/issues/532 [TPAC 2018]
* w3c/mediacapture-record (+1/-1/💬1)
1 issues created:
- Should MediaRecorderOptions fields be optional? (by eliasmeire)
https://github.com/w3c/mediacapture-record/issues/156
1 issues received 1 new comments:
- #156 Should MediaRecorderOptions members be optional? (1 by eliasmeire)
https://github.com/w3c/mediacapture-record/issues/156
1 issues closed:
- Should MediaRecorderOptions members be optional? https://github.com/w3c/mediacapture-record/issues/156
* w3c/mediacapture-screen-share (+1/-4/💬19)
1 issues created:
- Forbid getDisplayMedia in top-level browsing context by default? (by jan-ivar)
https://github.com/w3c/mediacapture-screen-share/issues/90
9 issues received 19 new comments:
- #83 Event for screen sharing (8 by martinthomson, jan-ivar, jianjunz, youennf)
https://github.com/w3c/mediacapture-screen-share/issues/83 [enhancement]
- #90 Forbid getDisplayMedia in top-level browsing context by default? (4 by eric-carlson, martinthomson, jan-ivar, alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/90
- #66 Constraints for Captured Display Surfaces should move to MediaTrackSettings (1 by alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/66 [PR exists]
- #39 non-top-level browsing contexts (1 by alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/39 [PR exists]
- #77 Should getDisplayMedia be functional in SecureContext only? (1 by jan-ivar)
https://github.com/w3c/mediacapture-screen-share/issues/77 [Ready for PR] [TPAC 2018]
- #81 The user agent should be allowed to change sources after getDisplayMedia() resolves (1 by alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/81 [Ready for PR] [TPAC 2018]
- #82 Should getDisplayMedia be moved to navigator.mediaDevices (1 by alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/82 [PR exists] [TPAC 2018]
- #59 TAG review (1 by alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/59
- #31 define behaviors of all existing constraints that should apply in the screen capture (1 by alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/31 [PR exists] [TPAC 2018]
4 issues closed:
- non-top-level browsing contexts https://github.com/w3c/mediacapture-screen-share/issues/39 [PR exists]
- Should getDisplayMedia be moved to navigator.mediaDevices https://github.com/w3c/mediacapture-screen-share/issues/82 [PR exists] [TPAC 2018]
- define behaviors of all existing constraints that should apply in the screen capture https://github.com/w3c/mediacapture-screen-share/issues/31 [PR exists] [TPAC 2018]
- Should getDisplayMedia be functional in SecureContext only? https://github.com/w3c/mediacapture-screen-share/issues/77 [Ready for PR] [TPAC 2018]
* w3c/mst-content-hint (+0/-1/💬0)
1 issues closed:
- Repo needs Travis CI https://github.com/w3c/mst-content-hint/issues/26
Pull requests
-------------
* w3c/webrtc-pc (+1/-1/💬3)
1 pull requests submitted:
- Set [[Direction]] when doing SRD(answer). (by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2033
2 pull requests received 3 new comments:
- #2015 SVC Extension Specification (TPAC) (2 by caribouW3, aboba)
https://github.com/w3c/webrtc-pc/pull/2015 [enhancement]
- #2010 Add preferredPayloadType to RTCRtpCodecCapability (1 by alvestrand)
https://github.com/w3c/webrtc-pc/pull/2010 [Simulcast] [TPAC 2018]
1 pull requests merged:
- Set [[Direction]] when doing SRD(answer).
https://github.com/w3c/webrtc-pc/pull/2033
* w3c/webrtc-stats (+0/-0/💬2)
2 pull requests received 2 new comments:
- #379 add rtt to rtcdatachannelsstats (1 by alvestrand)
https://github.com/w3c/webrtc-stats/pull/379
- #372 add stunserverconnectionstats (1 by alvestrand)
https://github.com/w3c/webrtc-stats/pull/372
* w3c/webrtc-quic (+2/-2/💬8)
2 pull requests submitted:
- Added stream creation to use Promises. (by shampson)
https://github.com/w3c/webrtc-quic/pull/84
- Add errorCode and reason to RTCQuicTransport.stop() (by shampson)
https://github.com/w3c/webrtc-quic/pull/82
4 pull requests received 8 new comments:
- #73 Add support for client/server without ICE (5 by pthatcherg, annevk)
https://github.com/w3c/webrtc-quic/pull/73
- #76 Add support for unreliability (with parameters dictionary) (1 by pthatcherg)
https://github.com/w3c/webrtc-quic/pull/76
- #82 Add errorCode and reason to RTCQuicTransport.stop() (1 by shampson)
https://github.com/w3c/webrtc-quic/pull/82
- #84 Added stream creation to use Promises. (1 by shampson)
https://github.com/w3c/webrtc-quic/pull/84
2 pull requests merged:
- Add errorCode and reason to RTCQuicTransport.stop()
https://github.com/w3c/webrtc-quic/pull/82
- Add support for unreliability (with parameters dictionary)
https://github.com/w3c/webrtc-quic/pull/76
* w3c/mediacapture-output (+0/-1/💬0)
1 pull requests merged:
- Make setSinkId and sinkId SecureContext.
https://github.com/w3c/mediacapture-output/pull/81
* w3c/mediacapture-screen-share (+0/-1/💬0)
1 pull requests merged:
- Define and rely on "display-capture" permission-based feature policy.
https://github.com/w3c/mediacapture-screen-share/pull/87
* w3c/mst-content-hint (+1/-1/💬0)
1 pull requests submitted:
- Set up automatic quality check and automatic publication with Echidna (by dontcallmedom)
https://github.com/w3c/mst-content-hint/pull/27
1 pull requests merged:
- Set up automatic quality check and automatic publication with Echidna
https://github.com/w3c/mst-content-hint/pull/27
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, 20 November 2018 17:01:24 UTC