- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 20 Aug 2019 17:01:17 +0000
- To: public-webrtc@w3.org
- Message-Id: <E1i07VV-0003qr-BQ@uranus.w3.org>
Issues
------
* w3c/webrtc-pc (+3/-14/💬12)
3 issues created:
- Status of Document: Update "features at risk" list (by aboba)
https://github.com/w3c/webrtc-pc/issues/2275 [Editorial]
- ICE restart and terminal RTCIceTransport.state "failed" state (by henbos)
https://github.com/w3c/webrtc-pc/issues/2273
- stuns: usage in examples (by fippo)
https://github.com/w3c/webrtc-pc/issues/2270
10 issues received 12 new comments:
- #1732 WHATWG streams for data channel messages (2 by aboba)
https://github.com/w3c/webrtc-pc/issues/1732 [WebRTC NV]
- #1709 example 14: render before verifying the remote fingerprint? (2 by fippo, a2sheppy)
https://github.com/w3c/webrtc-pc/issues/1709 [Editorial] [PR exists]
- #2176 Spec steps on stop() underestimate BUNDLE problem. (1 by aboba)
https://github.com/w3c/webrtc-pc/issues/2176 [July 2019 Virtual Interim] [PR exists]
- #2145 createOffer does not guard against "have-remote-offer" (1 by aboba)
https://github.com/w3c/webrtc-pc/issues/2145 [Needs Test] [PR exists]
- #1575 Inconsistent setting of receiver.track.readyState violates Mediacapture (1 by dontcallmedom)
https://github.com/w3c/webrtc-pc/issues/1575 [Ready for PR] [TPAC 2018]
- #2248 degradationPreference is under-specified (1 by aboba)
https://github.com/w3c/webrtc-pc/issues/2248 [TPAC 2019]
- #1981 RTCIceTransport selected candidate pair behavior when changing state (1 by aboba)
https://github.com/w3c/webrtc-pc/issues/1981 [TPAC 2018]
- #1708 Example 14 never sends any media (1 by dontcallmedom)
https://github.com/w3c/webrtc-pc/issues/1708 [Editorial]
- #2254 Checks in https://w3c.github.io/webrtc-pc/#dom-RTCDTMFSender-insertDTMF could be simplified (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2254 [Editorial]
- #2173 Timing of setRemoteDescription's identity validation is unclear (1 by henbos)
https://github.com/w3c/webrtc-pc/issues/2173 [PR exists]
14 issues closed:
- Spec steps on stop() underestimate BUNDLE problem. https://github.com/w3c/webrtc-pc/issues/2176 [July 2019 Virtual Interim] [PR exists]
- createOffer does not guard against "have-remote-offer" https://github.com/w3c/webrtc-pc/issues/2145 [Needs Test] [PR exists]
- stuns: usage in examples https://github.com/w3c/webrtc-pc/issues/2270 [Editorial] [PR exists]
- No procedure for the ICE failed state https://github.com/w3c/webrtc-pc/issues/2004 [PR exists]
- Mark Oauth as a "feature at risk" https://github.com/w3c/webrtc-pc/issues/2246 [PR exists]
- Mark voiceActivityDetection and dtx as Feature At Risk (Was: Is voiceActivityDetection still needed?) https://github.com/w3c/webrtc-pc/issues/2236 [PR exists]
- Mark getSupportedAlgorithms as a "feature at risk" https://github.com/w3c/webrtc-pc/issues/2255 [PR exists]
- Example 14 never sends any media https://github.com/w3c/webrtc-pc/issues/1708 [Editorial] [PR exists]
- example 14: render before verifying the remote fingerprint? https://github.com/w3c/webrtc-pc/issues/1709 [Editorial] [PR exists]
- Too many test links in the spec, some redundant https://github.com/w3c/webrtc-pc/issues/2161 [Editorial] [PR exists]
- Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk" https://github.com/w3c/webrtc-pc/issues/2258 [PR exists]
- WHATWG streams for data channel messages https://github.com/w3c/webrtc-pc/issues/1732 [WebRTC NV]
- RTCDataChannel section structure https://github.com/w3c/webrtc-pc/issues/1847 [Editorial] [PR exists]
- Use consistent internal slot terminology (editorial) https://github.com/w3c/webrtc-pc/issues/2226 [Editorial] [PR exists]
* w3c/webrtc-stats (+6/-3/💬17)
6 issues created:
- Add metric for ICE reroutes (by henbos)
https://github.com/w3c/webrtc-stats/issues/474
- Issues with replaceTrack, will statsended fire or give me what I want. (by vr000m)
https://github.com/w3c/webrtc-stats/issues/472
- Rethinking "sender" and "receiver" stats (by henbos)
https://github.com/w3c/webrtc-stats/issues/471
- RTCMediaStreamStats can be made obsolete (by henbos)
https://github.com/w3c/webrtc-stats/issues/470
- New Respec issues (by vr000m)
https://github.com/w3c/webrtc-stats/issues/468
- Deleted was removed in #462, was not added to Obsolete section (by vr000m)
https://github.com/w3c/webrtc-stats/issues/467
8 issues received 17 new comments:
- #471 Rethinking "sender" and "receiver" stats (4 by henbos, vr000m, alvestrand)
https://github.com/w3c/webrtc-stats/issues/471
- #468 New Respec issues (3 by henbos)
https://github.com/w3c/webrtc-stats/issues/468 [PR exists]
- #445 We should move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats (3 by henbos, alvestrand)
https://github.com/w3c/webrtc-stats/issues/445 [Ready for PR]
- #472 Issues with replaceTrack, will statsended fire or give me what I want. (2 by henbos, alvestrand)
https://github.com/w3c/webrtc-stats/issues/472
- #474 Add metric for ICE reroutes (2 by jonasoreland, alvestrand)
https://github.com/w3c/webrtc-stats/issues/474
- #396 RTC[Audio/Video]SenderStats should have mid (1 by alvestrand)
https://github.com/w3c/webrtc-stats/issues/396 [CR blocker] [Ready for PR]
- #402 Move all stream stats from the "sender"/"receiver" stats (1 by henbos)
https://github.com/w3c/webrtc-stats/issues/402 [CR blocker] [PR exists]
- #467 Deleted was removed in #462, was not added to Obsolete section (1 by youennf)
https://github.com/w3c/webrtc-stats/issues/467
3 issues closed:
- We should move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats https://github.com/w3c/webrtc-stats/issues/445 [PR exists]
- New Respec issues https://github.com/w3c/webrtc-stats/issues/468 [PR exists]
- Move all stream stats from the "sender"/"receiver" stats https://github.com/w3c/webrtc-stats/issues/402 [CR blocker] [PR exists]
* w3c/webrtc-nv-use-cases (+2/-0/💬0)
2 issues created:
- Accessibility Use Cases (by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/45
- WHATWG streams for data channel messages (by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/44
* w3c/mediacapture-main (+0/-2/💬9)
5 issues received 9 new comments:
- #607 fixed, per origin, device ID creates tracking risk (4 by snyderp, alvestrand, youennf)
https://github.com/w3c/mediacapture-main/issues/607 [TPAC 2019]
- #605 MediaTrackSettings lacks support of channel layout (2 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/605
- #608 Is enumerateDevices list order significant? (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/608
- #610 Violation. (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/610
- #611 Remove "The relative order of the tracks in the set is User Agent defined and the API will never put any requirements on the order.", et al. (1 by alvestrand)
https://github.com/w3c/mediacapture-main/issues/611
2 issues closed:
- Remove "The relative order of the tracks in the set is User Agent defined and the API will never put any requirements on the order.", et al. https://github.com/w3c/mediacapture-main/issues/611 [enhancement]
- Violation. https://github.com/w3c/mediacapture-main/issues/610
* w3c/mediacapture-record (+1/-1/💬0)
1 issues created:
- Add method that allows user specification of which tracks go with what number in the container-dependent ordering (by guest271314)
https://github.com/w3c/mediacapture-record/issues/179
1 issues closed:
- Add method MediaRecorder.restart considering this use case. https://github.com/w3c/mediacapture-record/issues/178
* w3c/mediacapture-screen-share (+0/-1/💬12)
2 issues received 12 new comments:
- #105 Provide a means to select only part of a screen to capture (10 by henbos, guest271314, alvestrand, youennf)
https://github.com/w3c/mediacapture-screen-share/issues/105 [question]
- #108 Should the permissions UI be the first captured frame? (2 by guest271314, alvestrand)
https://github.com/w3c/mediacapture-screen-share/issues/108 [question]
1 issues closed:
- Provide a means to select only part of a screen to capture https://github.com/w3c/mediacapture-screen-share/issues/105 [question]
Pull requests
-------------
* w3c/webrtc-pc (+6/-12/💬11)
6 pull requests submitted:
- RTCIceTransport selected candidate pair behavior when changing state (by aboba)
https://github.com/w3c/webrtc-pc/pull/2276
- Change "stuns" to "stun" in examples (by aboba)
https://github.com/w3c/webrtc-pc/pull/2274
- Change "stuns" to "stun" in examples (by aboba)
https://github.com/w3c/webrtc-pc/pull/2272
- Remove example on media before signaling (by dontcallmedom)
https://github.com/w3c/webrtc-pc/pull/2271
- RTCIceTransport selected candidate pair behavior when changing state (by aboba)
https://github.com/w3c/webrtc-pc/pull/2269
- Effect of ICE failed state (by aboba)
https://github.com/w3c/webrtc-pc/pull/2268
6 pull requests received 11 new comments:
- #2266 Clarify example on example with media before signaling (4 by fippo, dontcallmedom, aboba)
https://github.com/w3c/webrtc-pc/pull/2266 [Editorial]
- #2269 RTCIceTransport selected candidate pair behavior when changing state (2 by henbos, aboba)
https://github.com/w3c/webrtc-pc/pull/2269
- #2175 Permission API for receive-only media and data use cases (2 by lgrahl, youennf)
https://github.com/w3c/webrtc-pc/pull/2175 [June 2019 Virtual Interim]
- #2261 Mark RTCRtpEncodingParameters.maxFramerate as "feature at risk" (1 by henbos)
https://github.com/w3c/webrtc-pc/pull/2261
- #2259 Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk" (1 by lgrahl)
https://github.com/w3c/webrtc-pc/pull/2259
- #2222 Add initialization of DataChannelId on connection (1 by alvestrand)
https://github.com/w3c/webrtc-pc/pull/2222 [Editors can integrate] [Needs submitter action]
12 pull requests merged:
- Change "stuns" to "stun" in examples
https://github.com/w3c/webrtc-pc/pull/2274
- Remove example on media before signaling
https://github.com/w3c/webrtc-pc/pull/2271
- Effect of ICE failed state
https://github.com/w3c/webrtc-pc/pull/2268
- Add a test-coverage focused view to the spec
https://github.com/w3c/webrtc-pc/pull/2262
- Mark RTCDataChannel/RTCRtpSendParameters.priority as "feature at risk"
https://github.com/w3c/webrtc-pc/pull/2259
- Mark getSupportedAlgorithms as a "feature at risk"
https://github.com/w3c/webrtc-pc/pull/2256
- Clear [[LastCreatedOffer/Answer]] in SRD(answer) as well (editorial)
https://github.com/w3c/webrtc-pc/pull/2252 [Editorial]
- Mark OAuth as a "feature at risk"
https://github.com/w3c/webrtc-pc/pull/2247
- Mark VAD and dtx as "features at risk"
https://github.com/w3c/webrtc-pc/pull/2245
- Add sub-structure to data channel description
https://github.com/w3c/webrtc-pc/pull/2265 [Editorial]
- Properly sort simulcast layers in example by size
https://github.com/w3c/webrtc-pc/pull/2267 [Editorial]
- Use consistent notation for internal slots
https://github.com/w3c/webrtc-pc/pull/2264 [Editorial]
* w3c/webrtc-stats (+3/-4/💬6)
3 pull requests submitted:
- Adds RTCTransportStats.selectedCandidatePairChanges (by henbos)
https://github.com/w3c/webrtc-stats/pull/475
- Move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats.[decoder/encoder]Implementation (by henbos)
https://github.com/w3c/webrtc-stats/pull/473
- Fix respec issues (by henbos)
https://github.com/w3c/webrtc-stats/pull/469
4 pull requests received 6 new comments:
- #466 Move "receiver" stats to "inbound-rtp" (2 by henbos, vr000m)
https://github.com/w3c/webrtc-stats/pull/466
- #475 Adds RTCTransportStats.selectedCandidatePairChanges (2 by jonasoreland, henbos)
https://github.com/w3c/webrtc-stats/pull/475
- #469 Fix respec issues (1 by henbos)
https://github.com/w3c/webrtc-stats/pull/469
- #473 Move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats.[decoder/encoder]Implementation (1 by henbos)
https://github.com/w3c/webrtc-stats/pull/473
4 pull requests merged:
- Move RTCCodecStats.implementation to RTC[In/Out]boundRtpStreamStats.[decoder/encoder]Implementation
https://github.com/w3c/webrtc-stats/pull/473
- Fix respec issues
https://github.com/w3c/webrtc-stats/pull/469
- Move "receiver" stats to "inbound-rtp"
https://github.com/w3c/webrtc-stats/pull/466
- Move "sender" stats to "outbound-rtp", "inbound-rtp" and "media-source"
https://github.com/w3c/webrtc-stats/pull/463
* w3c/mediacapture-main (+0/-2/💬2)
2 pull requests received 2 new comments:
- #591 Recommend UUID for deviceId and groupId (1 by youennf)
https://github.com/w3c/mediacapture-main/pull/591 [Editors can integrate]
- #595 Interpret the empty string as if the constraint is not specified (1 by youennf)
https://github.com/w3c/mediacapture-main/pull/595 [Editors can integrate] [June 2019 interim]
2 pull requests merged:
- Interpret the empty string as if the constraint is not specified
https://github.com/w3c/mediacapture-main/pull/595 [Editors can integrate] [June 2019 interim]
- Recommend UUID for deviceId and groupId
https://github.com/w3c/mediacapture-main/pull/591 [Editors can integrate]
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-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 August 2019 17:01:20 UTC