- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 06 Aug 2019 17:01:16 +0000
- To: public-webrtc@w3.org
- Message-Id: <E1hv2po-0005at-Gq@uranus.w3.org>
Issues
------
* w3c/webrtc-pc (+8/-14/💬28)
8 issues created:
- Considering making RTCCertificate throw when serialized when _forStorage_ is false (by annevk)
https://github.com/w3c/webrtc-pc/issues/2257
- Mark getSupportedAlgorithms as a "feature at risk" (by aboba)
https://github.com/w3c/webrtc-pc/issues/2255 [PR exists]
- Checks in https://w3c.github.io/webrtc-pc/#dom-RTCDTMFSender-insertDTMF could be simplified (by youennf)
https://github.com/w3c/webrtc-pc/issues/2254
- RTCDTMFToneChangeEventInit.tone is required (by youennf)
https://github.com/w3c/webrtc-pc/issues/2253
- degradationPreference is under-specified (by aboba)
https://github.com/w3c/webrtc-pc/issues/2248
- Mark Oauth as a "feature at risk" (by aboba)
https://github.com/w3c/webrtc-pc/issues/2246
- Control surface for header extensions (by henbos)
https://github.com/w3c/webrtc-pc/issues/2243
- setRemoteDescription(): Is parameter optional or not? (by a2sheppy)
https://github.com/w3c/webrtc-pc/issues/2242
12 issues received 28 new comments:
- #2240 Clarify that getSynchronizationSources() should return information even if the track has no sink (<video> tag) (8 by henbos, chxg, jan-ivar)
https://github.com/w3c/webrtc-pc/issues/2240 [Ready for PR]
- #2243 Control surface for header extensions (5 by henbos, alvestrand, aboba, Orphis)
https://github.com/w3c/webrtc-pc/issues/2243 [WebRTC NV]
- #2241 API for codec performance (4 by henbos, aboba)
https://github.com/w3c/webrtc-pc/issues/2241 [WebRTC NV]
- #1745 Codify refusing to generate an empty Offer (2 by jan-ivar, alvestrand)
https://github.com/w3c/webrtc-pc/issues/1745 [Needs PR]
- #2238 Nulling mid when m-line is recycled is surprising. (2 by jan-ivar, alvestrand)
https://github.com/w3c/webrtc-pc/issues/2238 [PR exists]
- #2242 setRemoteDescription(): Is parameter optional or not? (1 by a2sheppy)
https://github.com/w3c/webrtc-pc/issues/2242
- #2022 callback-based https://w3c.github.io/webrtc-pc/#method-extensions are not covered by WPT tests (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2022 [Needs Test] [question]
- #2055 Send transferable data (1 by aboba)
https://github.com/w3c/webrtc-pc/issues/2055 [WebRTC NV]
- #2248 degradationPreference is under-specified (1 by Orphis)
https://github.com/w3c/webrtc-pc/issues/2248
- #2215 Order of multiple RTCDataChannel.send calls in case of blobs (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/2215 [Editorial]
- #1972 Make possible to select TURN allocation address family (to avoid IPv6 confusion) (1 by alvestrand)
https://github.com/w3c/webrtc-pc/issues/1972 [Chair decision needed]
- #1277 Section 4.3.1: operations queue and setDescription (1 by jan-ivar)
https://github.com/w3c/webrtc-pc/issues/1277
14 issues closed:
- Section 4.3.1: operations queue and setDescription https://github.com/w3c/webrtc-pc/issues/1277
- Codify refusing to generate an empty Offer https://github.com/w3c/webrtc-pc/issues/1745 [Needs PR]
- Send transferable data https://github.com/w3c/webrtc-pc/issues/2055 [WebRTC NV]
- API for codec performance https://github.com/w3c/webrtc-pc/issues/2241 [WebRTC NV]
- RTCIceTransport.getRemoteCandidates() does not return prflx candidates https://github.com/w3c/webrtc-pc/issues/2124 [Chair decision needed] [wontfix]
- callback-based https://w3c.github.io/webrtc-pc/#method-extensions are not covered by WPT tests https://github.com/w3c/webrtc-pc/issues/2022 [Needs Test] [question]
- Missing CNAME in RID based simulcast offer https://github.com/w3c/webrtc-pc/issues/2114 [question]
- More simulcast examples https://github.com/w3c/webrtc-pc/issues/2035 [Chair decision needed] [Simulcast]
- Make possible to select TURN allocation address family (to avoid IPv6 confusion) https://github.com/w3c/webrtc-pc/issues/1972 [Chair decision needed]
- transceiver.direction doesn’t respond, if out-of-sync. https://github.com/w3c/webrtc-pc/issues/1940 [TPAC 2018]
- transceiver.direction doesn’t respond, if out-of-sync. https://github.com/w3c/webrtc-pc/issues/1940 [TPAC 2018]
- Control surface for header extensions https://github.com/w3c/webrtc-pc/issues/2243 [WebRTC NV]
- Nulling mid when m-line is recycled is surprising. https://github.com/w3c/webrtc-pc/issues/2238 [PR exists]
- setRemoteDescription(): Is parameter optional or not? https://github.com/w3c/webrtc-pc/issues/2242
* w3c/webrtc-stats (+0/-0/💬3)
2 issues received 3 new comments:
- #465 Measuring background noise (energy) (2 by vr000m, aboba)
https://github.com/w3c/webrtc-stats/issues/465
- #432 OPUS -- Exposing SILK or CELT mode in getStats (1 by mvarela)
https://github.com/w3c/webrtc-stats/issues/432
* w3c/webrtc-nv-use-cases (+4/-0/💬3)
4 issues created:
- Use case with 5G edge computing (by jianjunz)
https://github.com/w3c/webrtc-nv-use-cases/issues/43
- Send transferable data (by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/42
- API for codec performance (by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/41
- Control surface for header extensions (by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/40
2 issues received 3 new comments:
- #43 Use case with 5G edge computing (2 by dontcallmedom, jianjunz)
https://github.com/w3c/webrtc-nv-use-cases/issues/43
- #40 Control surface for header extensions (1 by aboba)
https://github.com/w3c/webrtc-nv-use-cases/issues/40
* w3c/mediacapture-record (+1/-2/💬5)
1 issues created:
- Ability to tell MediaRecorder to maximize frame rate (by j0000el)
https://github.com/w3c/mediacapture-record/issues/177
2 issues received 5 new comments:
- #177 Ability to tell MediaRecorder to maximize frame rate (3 by j0000el, jesup, alvestrand)
https://github.com/w3c/mediacapture-record/issues/177
- #173 Input video track width and height MUST be recorded and playable (2 by guest271314, alvestrand)
https://github.com/w3c/mediacapture-record/issues/173
2 issues closed:
- What are the default bitrate attribute values? https://github.com/w3c/mediacapture-record/issues/169
- Clarification needed for mime type handling https://github.com/w3c/mediacapture-record/issues/170
* w3c/mediacapture-screen-share (+0/-1/💬4)
2 issues received 4 new comments:
- #81 The user agent should be allowed to change sources after getDisplayMedia() resolves (3 by jan-ivar, aboba)
https://github.com/w3c/mediacapture-screen-share/issues/81 [Ready for PR] [TPAC 2018]
- #107 Screenshot (still image) capability (1 by henbos)
https://github.com/w3c/mediacapture-screen-share/issues/107 [question]
1 issues closed:
- Screenshot (still image) capability https://github.com/w3c/mediacapture-screen-share/issues/107 [question]
Pull requests
-------------
* w3c/webrtc-pc (+8/-1/💬4)
8 pull requests submitted:
- Mark getSupportedAlgorithms as a "feature at risk" (by aboba)
https://github.com/w3c/webrtc-pc/pull/2256
- Clear [[LastCreatedOffer/Answer]] in SRD(answer) as well (editorial) (by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2252
- Don't fire SRD() events until target peer identity has been verified. (by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2251
- Clarify SRD() won't reject on identity failure wo/target peer identity. (by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2250
- Add a [[DocumentOrigin]] internal slot to RTCPeerConnection. (by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2249
- Mark OAuth as a "feature at risk" (by aboba)
https://github.com/w3c/webrtc-pc/pull/2247
- Mark VAD and dtx as "features at risk" (by aboba)
https://github.com/w3c/webrtc-pc/pull/2245
- Infer SLD type from signalingState inside chained steps. (by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2244
3 pull requests received 4 new comments:
- #2175 Permission API for receive-only media and data use cases (2 by lgrahl, alvestrand)
https://github.com/w3c/webrtc-pc/pull/2175 [June 2019 Virtual Interim]
- #2249 Add a [[DocumentOrigin]] internal slot to RTCPeerConnection. (1 by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2249
- #2239 Don't clear mid property if stopped. (1 by jan-ivar)
https://github.com/w3c/webrtc-pc/pull/2239
1 pull requests merged:
- Infer SLD type from signalingState inside chained steps.
https://github.com/w3c/webrtc-pc/pull/2244
* w3c/webrtc-nv-use-cases (+0/-0/💬1)
1 pull requests received 1 new comments:
- #14 N29: A way to obtain user consent for one-way media and data use cases (1 by lgrahl)
https://github.com/w3c/webrtc-nv-use-cases/pull/14 [June 2019 Interim] [Submitter Action Needed]
* w3c/mediacapture-record (+0/-2/💬1)
1 pull requests received 1 new comments:
- #175 Define behavior for all bitsPerSecond attributes (1 by Pehrsons)
https://github.com/w3c/mediacapture-record/pull/175 [Editors can integrate]
2 pull requests merged:
- Define behavior for all bitsPerSecond attributes
https://github.com/w3c/mediacapture-record/pull/175 [Editors can integrate]
- Clarify MediaRecorder's mimeType handling
https://github.com/w3c/mediacapture-record/pull/171
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, 6 August 2019 17:01:19 UTC