Weekly github digest (WebRTC WG specifications) from W3C Webmaster via GitHub API on 2023-12-12 (public-webrtc@w3.org from December 2023)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 12 Dec 2023 17:00:22 +0000
To: public-webrtc@w3.org
Message-Id: <E1rD67K-009OtO-6b@uranus.w3.org>
Issues
------
* w3c/webrtc-pc (+1/-1/💬7)
  1 issues created:
  - Composed RTCPeerConnection.gatheringState seems wrong in some ICE restart cases (by docfaraday)
    https://github.com/w3c/webrtc-pc/issues/2914 

  4 issues received 7 new comments:
  - #2914 Composed RTCPeerConnection.gatheringState seems wrong in some ICE restart cases (4 by alvestrand, docfaraday, fippo)
    https://github.com/w3c/webrtc-pc/issues/2914 
  - #2822 RTCSctpTransport.maxMessageSize is a floating point type (1 by docfaraday)
    https://github.com/w3c/webrtc-pc/issues/2822 
  - #2751 Intended outcome when modifying direction in have-local-offer (1 by mickel8)
    https://github.com/w3c/webrtc-pc/issues/2751 [Needs Test] [Ready for PR] [July virtual interim] 
  - #2170 data channel default binaryType value is 'blob' (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-pc/issues/2170 [Ready for PR] 

  1 issues closed:
  - RTCSctpTransport.maxMessageSize is a floating point type https://github.com/w3c/webrtc-pc/issues/2822 

* w3c/webrtc-nv-use-cases (+0/-0/💬7)
  7 issues received 7 new comments:
  - #103 Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/103 [PR exists] [TPAC 2023] 
  - #95 Low Latency Streaming: Review of requirements (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/95 [duplicate] 
  - #94 Section 3.2.1: Improvements for game pad input (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/94 [July 2023 Virtual Interim] 
  - #91 N15 latency control should be formulated in a technology-agnostic way (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/91 
  - #86 Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/86 
  - #85 What is a "node" in the Low latency Broadcast with Fanout use case? (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/85 
  - #80 Access to raw audio data (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/issues/80 [TPAC 2023] 

* w3c/mediacapture-main (+1/-0/💬8)
  1 issues created:
  - Avoid circular definition of muted. (by jan-ivar)
    https://github.com/w3c/mediacapture-main/issues/982 

  1 issues received 8 new comments:
  - #982 Avoid circular definition of muted. (8 by eladalon1983, guidou, jan-ivar, youennf)
    https://github.com/w3c/mediacapture-main/issues/982 

* w3c/mediacapture-screen-share (+0/-0/💬1)
  1 issues received 1 new comments:
  - #281 Distinguish cancellations from absent OS permissions (1 by jan-ivar)
    https://github.com/w3c/mediacapture-screen-share/issues/281 

* w3c/webrtc-svc (+0/-0/💬3)
  2 issues received 3 new comments:
  - #45 Move to Candidate Recommendation (2 by aboba, dontcallmedom)
    https://github.com/w3c/webrtc-svc/issues/45 
  - #3 Custom Scalability Structures (1 by aboba)
    https://github.com/w3c/webrtc-svc/issues/3 [enhancement] 

* w3c/webrtc-extensions (+1/-3/💬0)
  1 issues created:
  - Add API to control encode complexity (by ssilkin)
    https://github.com/w3c/webrtc-extensions/issues/191 

  3 issues closed:
  - icecandidatepairadd is fired on closed pc https://github.com/w3c/webrtc-extensions/issues/176 
  - What does it mean to NOT nominate candidatePair? https://github.com/w3c/webrtc-extensions/issues/179 
  - setSelectedCandidatePair should explicitly reference the RTCIceTransport algorithm for change in selected candidate pair https://github.com/w3c/webrtc-extensions/issues/185 

* w3c/webrtc-encoded-transform (+2/-2/💬20)
  2 issues created:
  - Internal slots are not defined (by saschanaz)
    https://github.com/w3c/webrtc-encoded-transform/issues/218 
  - WHATWG Streams have no `[[owner]]` but the spec sets it (by saschanaz)
    https://github.com/w3c/webrtc-encoded-transform/issues/217 

  3 issues received 20 new comments:
  - #217 WHATWG Streams have no `[[owner]]` but the spec sets it (7 by alvestrand, dontcallmedom, saschanaz, youennf)
    https://github.com/w3c/webrtc-encoded-transform/issues/217 
  - #211 Is frame-level fanout in scope of WebRTC encoded transform? (7 by alvestrand, guidou, jan-ivar, youennf)
    https://github.com/w3c/webrtc-encoded-transform/issues/211 
  - #89 Generalize ScriptTransform constructor to allow main-thread processing (6 by alvestrand, guidou, jan-ivar, youennf)
    https://github.com/w3c/webrtc-encoded-transform/issues/89 

  2 issues closed:
  - Expose flow control information to transform https://github.com/w3c/webrtc-encoded-transform/issues/206 [enhancement] 
  - WHATWG Streams have no `[[owner]]` but the spec sets it https://github.com/w3c/webrtc-encoded-transform/issues/217 

* w3c/webrtc-rtptransport (+0/-0/💬9)
  9 issues received 9 new comments:
  - #15 Examples pipe multiple streams into a single writable (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/15 [PR Exists] 
  - #14 Update examples to use standard APIs (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/14 
  - #13 Workers (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/13 
  - #12 Arbitrary RTP Header Extensions (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/12 
  - #11 Arbitrary RTCP messages (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/11 
  - #10 SDP "Bumper lanes" (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/10 
  - #9 Customizing piecemeal (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/9 
  - #8 WHATWG Streams support? (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/8 
  - #7 How does cryptex work? (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-rtptransport/issues/7 



Pull requests
-------------
* w3c/webrtc-pc (+1/-1/💬1)
  1 pull requests submitted:
  - Change the default value of binaryType to "arraybuffer" (by Orphis)
    https://github.com/w3c/webrtc-pc/pull/2913 

  1 pull requests received 1 new comments:
  - #2913 Change the default value of binaryType to "arraybuffer" (1 by alvestrand)
    https://github.com/w3c/webrtc-pc/pull/2913 

  1 pull requests merged:
  - Change the default value of binaryType to "arraybuffer"
    https://github.com/w3c/webrtc-pc/pull/2913 [Editors can integrate] 

* w3c/webrtc-stats (+1/-0/💬1)
  1 pull requests submitted:
  - Remove audio capture stats that have moved to MediaStreamTrack's stats (by henbos)
    https://github.com/w3c/webrtc-stats/pull/773 

  1 pull requests received 1 new comments:
  - #773 Remove audio capture stats that have moved to MediaStreamTrack's stats (1 by henbos)
    https://github.com/w3c/webrtc-stats/pull/773 

* w3c/webrtc-nv-use-cases (+0/-2/💬7)
  5 pull requests received 7 new comments:
  - #126 Further clarify cloud gaming (1 by stefhak)
    https://github.com/w3c/webrtc-nv-use-cases/pull/126 
  - #125 Clarify Requirement N37 (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/pull/125 [November VI] 
  - #124 Requirement N38 is satisfied by jitterBufferTarget (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/pull/124 [Editors can integrate] 
  - #123 Section 3.2.2: Clarify Use Case (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-nv-use-cases/pull/123 [November VI] 
  - #118 Section 3.2.1: Clarify Game streaming requirements (3 by dontcallmedom-bot, stefhak, xingri)
    https://github.com/w3c/webrtc-nv-use-cases/pull/118 [December 5 VI] 

  2 pull requests merged:
  - Section 3.2.2: Clarify Use Case
    https://github.com/w3c/webrtc-nv-use-cases/pull/123 [December 5 VI] 
  - Clarify Requirement N37
    https://github.com/w3c/webrtc-nv-use-cases/pull/125 [December 5 VI] 

* w3c/webrtc-extensions (+0/-3/💬1)
  1 pull requests received 1 new comments:
  - #175 Add RTCIceTransport method to remove candidate pairs (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-extensions/pull/175 [TPAC 2023] 

  3 pull requests merged:
  - Don't fire icecandidatepairadd if closed + avoid competing normative prose
    https://github.com/w3c/webrtc-extensions/pull/177 [editors can integrate] 
  - Move non-normative prose in nominate algo into a note.
    https://github.com/w3c/webrtc-extensions/pull/189 [editors can integrate] 
  - Refer to change of selected pair/state algo
    https://github.com/w3c/webrtc-extensions/pull/190 

* w3c/webrtc-encoded-transform (+1/-5/💬5)
  1 pull requests submitted:
  - Readable and Writable [[owner]] slots are unused (by youennf)
    https://github.com/w3c/webrtc-encoded-transform/pull/219 

  2 pull requests received 5 new comments:
  - #215 Add an API for a "keyframe has been requested" event (4 by alvestrand, dontcallmedom)
    https://github.com/w3c/webrtc-encoded-transform/pull/215 [Editors can integrate] 
  - #212 Describe "data" attribute (1 by dontcallmedom-bot)
    https://github.com/w3c/webrtc-encoded-transform/pull/212 

  5 pull requests merged:
  - Congestion control API proposal
    https://github.com/w3c/webrtc-encoded-transform/pull/207 
  - Add an API for a "keyframe has been requested" event
    https://github.com/w3c/webrtc-encoded-transform/pull/215 [Editors can integrate] 
  - Describe "data" attribute
    https://github.com/w3c/webrtc-encoded-transform/pull/212 
  - Update references and remove empty section
    https://github.com/w3c/webrtc-encoded-transform/pull/213 [editorial] 
  - Readable and Writable [[owner]] slots are unused
    https://github.com/w3c/webrtc-encoded-transform/pull/219 

* w3c/mediacapture-transform (+0/-1/💬0)
  1 pull requests merged:
  - Update audio explainer with intro + WebIDL
    https://github.com/w3c/mediacapture-transform/pull/75 

* w3c/mediacapture-region (+1/-1/💬1)
  1 pull requests submitted:
  - Demo - fix video size (by eladalon1983)
    https://github.com/w3c/mediacapture-region/pull/80 [Editorial] 

  1 pull requests received 1 new comments:
  - #80 Demo - fix video size (1 by eladalon1983)
    https://github.com/w3c/mediacapture-region/pull/80 [Editorial] 

  1 pull requests merged:
  - Demo - fix video size
    https://github.com/w3c/mediacapture-region/pull/80 [Editorial] 


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-priority
* 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-fromelement
* https://github.com/w3c/mediacapture-output
* https://github.com/w3c/mediacapture-screen-share
* https://github.com/w3c/mst-content-hint
* https://github.com/w3c/webrtc-svc
* https://github.com/w3c/webrtc-extensions
* https://github.com/w3c/webrtc-provisional-stats
* https://github.com/w3c/webrtc-encoded-transform
* https://github.com/w3c/mediacapture-automation
* https://github.com/w3c/mediacapture-transform
* https://github.com/w3c/mediacapture-region
* https://github.com/w3c/mediacapture-handle
* https://github.com/w3c/mediacapture-viewport
* https://github.com/w3c/webrtc-rtptransport
* https://github.com/web-platform-tests/wpt


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 December 2023 17:00:24 UTC