Web Real-Time Communications Working Group - Activity in 2024
No matches.
TR publications
-
3 documents published.
-
Media Capture and Streams published twice as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Screen Capture published as a Working Draft. History of Screen Capture
-
Past meetings
-
1 meeting.
GitHub
w3c/mediacapture-main
-
1 issue opened.
-
currentTime still references undefined "playing" state w3c/mediacapture-main#1024, by @jan-ivar.
-
-
1 issue closed.
-
currentTime still references undefined "playing" state w3c/mediacapture-main#1024.
-
-
1 issue received 4 new comments.
-
What is the purpose of requiring a successful gUM call before enumerateDevices? w3c/mediacapture-main#1019 (4 comments by @dontcallmedom-bot, @fippo, @jan-ivar)
-
-
4 pull requests opened.
-
Update to latest ReSpec version 35.2.2 w3c/mediacapture-main#1026, by @dontcallmedom.
-
Missed a spot that should use HTMLMediaElement's potentially playing definition w3c/mediacapture-main#1025, by @jan-ivar.
-
Update to latest ReSpec version 35.2.0 w3c/mediacapture-main#1023, by @dontcallmedom.
-
Prevent remove-a-track to recurse. w3c/mediacapture-main#1022, by @Kaiido.
-
-
3 pull requests merged.
-
Missed a spot that should use HTMLMediaElement's potentially playing definition w3c/mediacapture-main#1025.
-
Update to latest ReSpec version 35.2.0 w3c/mediacapture-main#1023.
-
Prevent remove-a-track to recurse. w3c/mediacapture-main#1022.
-
-
2 pull requests received 5 new comments.
-
Prevent remove-a-track to recurse. w3c/mediacapture-main#1022 (4 comments by @dontcallmedom, @Kaiido, @w3cbot)
-
Missed a spot that should use HTMLMediaElement's potentially playing definition w3c/mediacapture-main#1025 (1 comment by @dontcallmedom)
-
w3c/webrtc-pc
-
3 issues opened.
-
Use USVString for url attributes and members w3c/webrtc-pc#3029, by @dontcallmedom.
-
What holds on to RTCOfferOptions and its iceRestart member w3c/webrtc-pc#3028, by @gsnedders.
-
Legacy Interface Extensions is somewhat unclear w3c/webrtc-pc#3027, by @gsnedders.
-
-
3 issues received 3 new comments.
-
Spec says to send black frames for ended tracks w3c/webrtc-pc#3014 (1 comment by @dontcallmedom-bot)
-
Should we specify how addStream()/"addstream event" should behave? w3c/webrtc-pc#568 (1 comment by @gsnedders)
-
-
2 pull requests opened.
-
Update to ReSpec version 35.2.2 w3c/webrtc-pc#3030, by @dontcallmedom.
-
Update to ReSpec version 35.2.0 w3c/webrtc-pc#3026, by @dontcallmedom.
-
-
1 pull request merged.
-
Update to ReSpec version 35.2.0 w3c/webrtc-pc#3026.
-
-
2 pull requests received 5 new comments.
w3c/mst-content-hint
-
3 issues received 6 new comments.
-
Should the spec provide guideline on the default degradation preference to use for capture tracks? w3c/mst-content-hint#60 (2 comments by @jan-ivar)
-
What is the value of degradationPreference over time? (replaceTrack, contentHint setter) w3c/mst-content-hint#36 (1 comment by @jan-ivar)
w3c/mediacapture-screen-share
-
1 issue opened.
-
Missing spec-compliant way to detect shareable surfaces w3c/mediacapture-screen-share#309, by @eladalon1983.
-
-
1 issue closed.
-
Should screen capture tracks expose deviceId? w3c/mediacapture-screen-share#308.
-
-
1 issue received 4 new comments.
-
Should screen capture tracks expose deviceId? w3c/mediacapture-screen-share#308 (4 comments by @dontcallmedom-bot, @jan-ivar, @youennf)
-
-
1 pull request opened.
-
Add deviceId as settings and constraints for screen share video tracks. w3c/mediacapture-screen-share#310, by @youennf.
-
-
1 pull request merged.
-
Add deviceId as settings and constraints for screen share video tracks. w3c/mediacapture-screen-share#310.
-
-
1 pull request received 3 new comments.
-
Add deviceId as settings and constraints for screen share video tracks. w3c/mediacapture-screen-share#310 (3 comments by @handellm, @youennf)
-
w3c/webrtc-extensions
-
3 issues received 3 new comments.
-
receiver.hardwareAcceleration attribute instead of disableHardware[En|De]coding() static method w3c/webrtc-extensions#229 (1 comment by @aboba)
-
captureTimestamp: RTCRtpContributingSource vs RTCRtpSynchronizationSource w3c/webrtc-extensions#215 (1 comment by @lukehb)
-
1 pull request received 3 new comments.
-
Add WebRTC-specific interactions with capture/receive/RTP timestamps w3c/webrtc-extensions#224 (3 comments by @alvestrand, @handellm)
-
w3c/mediacapture-transform
-
1 issue closed.
-
MediaStreamTrackGenerator/MediaStream should buffer the current frame w3c/mediacapture-transform#114.
-
-
4 issues received 14 new comments.
-
We shouldn't require track transferability w3c/mediacapture-transform#113 (8 comments by @guidou, @jan-ivar, @youennf)
-
Track transferability requirement adds complexity to some common use cases w3c/mediacapture-transform#116 (3 comments by @guidou, @jan-ivar)
-
What is the expected timing of MSTP video frame enqueuing with other track events (configurationchange, applyConstraints promise resolution) w3c/mediacapture-transform#115 (2 comments by @dontcallmedom-bot, @jan-ivar)
-
MediaStreamTrackGenerator/MediaStream should buffer the current frame w3c/mediacapture-transform#114 (1 comment by @aboba)
-
w3c/mediacapture-surface-control
-
2 issues opened.
-
Where do forwarded "wheel" events fire? w3c/mediacapture-surface-control#51, by @tidoust.
-
Clarify "fire a blank event" for "capturedzoomlevelchange" w3c/mediacapture-surface-control#50, by @tidoust.
-
-
3 issues received 4 new comments.
-
Where do forwarded "wheel" events fire? w3c/mediacapture-surface-control#51 (2 comments by @eladalon1983, @tidoust)
-
Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? w3c/mediacapture-surface-control#45 (1 comment by @jan-ivar)
-
Clarify "fire a blank event" for "capturedzoomlevelchange" w3c/mediacapture-surface-control#50 (1 comment by @eladalon1983)
-
w3c/webrtc-rtptransport
-
1 issue opened.
-
Packet sender needs to expose a signal about max packet size w3c/webrtc-rtptransport#83, by @sprangerik.
-
-
3 issues received 3 new comments.
-
Should RTCRtpTransport(Processor) use event handlers for packet notifications? w3c/webrtc-rtptransport#70 (1 comment by @henbos)
-
Per-packet notifications are mandatory, this is not ideal for context switching w3c/webrtc-rtptransport#78 (1 comment by @henbos)
-
API creates per-packet temporary objects, this is not ideal for GC w3c/webrtc-rtptransport#77 (1 comment by @henbos)
-
-
1 pull request received 4 new comments.
w3c/mediacapture-output
-
1 issue received 10 new comments.
-
Implicit consent via getUserMedia should allow access to non-miked speakers w3c/mediacapture-output#147 (10 comments by @dontcallmedom-bot, @guidou, @jan-ivar, @youennf)
-
w3c/mediacapture-screen-share-extensions
-
2 issues received 10 new comments.
-
Auto-pause for Captured Surface Switching (2nd edition) w3c/mediacapture-screen-share-extensions#15 (8 comments by @dontcallmedom-bot, @jan-ivar, @tovepet, @youennf)
-
Cross-Type Surface Switching w3c/mediacapture-screen-share-extensions#16 (2 comments by @dontcallmedom-bot, @tovepet)
-
w3c/mediacapture-extensions
-
1 issue received 1 new comment.
-
Reduce scope of MediaStreamTrack transfer to DedicatedWorker for now w3c/mediacapture-extensions#158 (1 comment by @dontcallmedom-bot)
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
add receiveTime to metadata w3c/webrtc-encoded-transform#235, by @guidou.
-
-
1 issue received 1 new comment.
-
1 pull request received 4 new comments.
-
Add captureTimestamp and senderCaptureTimeOffset to frame metadata w3c/webrtc-encoded-transform#228 (4 comments by @aboba, @guidou, @jan-ivar, @youennf)
-
w3c/mediacapture-record
-
1 issue received 4 new comments.
-
Add replaceTrack method to MediaStream w3c/mediacapture-record#167 (4 comments by @alvestrand, @Kaiido)
-
TR publications
-
1 document published.
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Leah Tu (Microsoft Corporation) joined.
-
Bryant Chandler (Google LLC) joined.
-
-
1 participant left.
-
Srikanth Kambhatla (Intel Corporation) left.
-
GitHub
w3c/mediacapture-extensions
-
1 issue opened.
-
"dictionary Segment" is overly generic w3c/mediacapture-extensions#160, by @marcoscaceres.
-
-
1 pull request opened.
-
Add a section for the background blur field in VideoFrameMetadata w3c/mediacapture-extensions#159, by @markafoltz.
-
-
1 pull request received 12 new comments.
-
Add a section for the background blur field in VideoFrameMetadata w3c/mediacapture-extensions#159 (12 comments by @aboba, @brychanrobot, @eladalon1983, @markafoltz)
-
w3c/mediacapture-output
-
1 issue received 4 new comments.
-
Implicit consent via getUserMedia should allow access to non-miked speakers w3c/mediacapture-output#147 (4 comments by @guidou, @youennf)
-
w3c/mediacapture-fromelement
-
1 issue opened.
-
The value of `getSettings().frameRate` when captureStream(0) w3c/mediacapture-fromelement#102, by @Tackoil.
-
w3c/mediacapture-record
-
1 issue received 2 new comments.
-
Add replaceTrack method to MediaStream w3c/mediacapture-record#167 (2 comments by @EddyVinck, @ozturkkl)
-
-
1 pull request received 2 new comments.
w3c/webrtc-pc
-
7 issues opened.
-
How should be populated codecs capabilities fmtp lines? w3c/webrtc-pc#3024, by @youennf.
-
Clarify order of events when the SCTP transport is closed w3c/webrtc-pc#3022, by @jan-ivar.
-
Clarify that datachannel close is reflected remotely w3c/webrtc-pc#3021, by @jan-ivar.
-
Codec negotiation and level IDs w3c/webrtc-pc#3020, by @henbos.
-
Reconsider replaceTrack's blocking on the operations queue. w3c/webrtc-pc#3017, by @jan-ivar.
-
DataChannel connected step needs to queue a task w3c/webrtc-pc#3015, by @jan-ivar.
-
-
3 issues closed.
-
Align spec /w codec direction decision w3c/webrtc-pc#3006.
-
DataChannel connected step needs to queue a task w3c/webrtc-pc#3015.
-
-
10 issues received 34 new comments.
-
Codec negotiation and level IDs w3c/webrtc-pc#3020 (9 comments by @aboba, @dontcallmedom-bot, @henbos, @taste1981)
-
Missing resolution attributes from simulcast `addTransceiver` `sendEncodings` API enabling w3c/webrtc-pc#3019 (7 comments by @alvestrand, @henbos, @Orphis, @Santiago-Souto)
-
Reconsider replaceTrack's blocking on the operations queue. w3c/webrtc-pc#3017 (5 comments by @alvestrand, @dontcallmedom-bot, @jan-ivar)
-
Opus mono/stereo and remote track channelCount w3c/webrtc-pc#3010 (4 comments by @dontcallmedom-bot, @henbos)
-
How should be populated codecs capabilities fmtp lines? w3c/webrtc-pc#3024 (3 comments by @aboba, @alvestrand, @youennf)
-
Clarify order of events when the SCTP transport is closed w3c/webrtc-pc#3022 (1 comment by @dontcallmedom-bot)
-
-
4 pull requests opened.
-
Add remote track channelCount w3c/webrtc-pc#3025, by @henbos.
-
Allow level-id to be different in codec match w3c/webrtc-pc#3023, by @henbos.
-
Filter codecs preferences on transceiver direction w3c/webrtc-pc#3018, by @henbos.
-
Queue a task for the SCTP transport connected steps. w3c/webrtc-pc#3016, by @jan-ivar.
-
-
2 pull requests merged.
-
Filter codecs preferences on transceiver direction w3c/webrtc-pc#3018.
-
Queue a task for the SCTP transport connected steps. w3c/webrtc-pc#3016.
-
-
3 pull requests received 51 new comments.
-
Filter codecs preferences on transceiver direction w3c/webrtc-pc#3018 (25 comments by @dontcallmedom, @henbos, @jan-ivar)
-
Allow level-id to be different in codec match w3c/webrtc-pc#3023 (23 comments by @aboba, @alvestrand, @fippo, @henbos, @taste1981)
-
w3c/mediacapture-transform
-
3 issues opened.
-
Fire a stopped event on VideoTrackGenerator if all downstream tracks are stopped w3c/mediacapture-transform#117, by @jan-ivar.
-
Track transferability requirement adds complexity to some common use cases w3c/mediacapture-transform#116, by @guidou.
-
What is the expected timing of MSTP video frame enqueuing with other track events (configurationchange, applyConstraints promise resolution) w3c/mediacapture-transform#115, by @youennf.
-
-
1 issue closed.
-
Fire a stopped event on VideoTrackGenerator if all downstream tracks are stopped w3c/mediacapture-transform#117.
-
-
7 issues received 13 new comments.
-
Track transferability requirement adds complexity to some common use cases w3c/mediacapture-transform#116 (5 comments by @guidou, @jan-ivar, @youennf)
-
Fire a stopped event on VideoTrackGenerator if all downstream tracks are stopped w3c/mediacapture-transform#117 (2 comments by @jan-ivar, @youennf)
-
MediaStreamTrackGenerator/MediaStream should buffer the current frame w3c/mediacapture-transform#114 (2 comments by @dontcallmedom-bot, @youennf)
-
Playback and synchronization of MediaStreamTracks created by VideoTrack Generator w3c/mediacapture-transform#86 (1 comment by @dontcallmedom-bot)
-
Add "real-time" warning/note to VideoTrackGenerator w3c/mediacapture-transform#20 (1 comment by @dontcallmedom-bot)
-
Expectations/requirements for VideoFrame and AudioData timestamps w3c/mediacapture-transform#80 (1 comment by @dontcallmedom-bot)
-
What is the expected timing of MSTP video frame enqueuing with other track events (configurationchange, applyConstraints promise resolution) w3c/mediacapture-transform#115 (1 comment by @youennf)
-
w3c/webrtc-svc
-
2 issues opened.
-
scalabilityMode should be marked as existing only for video encodings w3c/webrtc-svc#106, by @fuzzy-coats.
-
RTCRtpSender.getCapabilities() should include scalability_modes in returned codec list w3c/webrtc-svc#105, by @taste1981.
-
-
1 issue closed.
-
1 issue received 2 new comments.
-
RTCRtpSender.getCapabilities() should include scalability_modes in returned codec list w3c/webrtc-svc#105 (2 comments by @alvestrand, @henbos)
-
w3c/webrtc-rtptransport
-
1 issue opened.
-
Support L4S RFC8888 w3c/webrtc-rtptransport#82, by @Orphis.
-
-
2 pull requests opened.
-
Packet sender receiver worker api w3c/webrtc-rtptransport#81, by @youennf.
-
Add RTCRtpTransportProcessor based API w3c/webrtc-rtptransport#80, by @youennf.
-
w3c/mediacapture-main
-
2 issues opened.
-
Does the channelCount attribute support a value greater than 2? w3c/mediacapture-main#1021, by @blogwy.
-
What is the order of events being track clones? w3c/mediacapture-main#1020, by @youennf.
-
-
1 issue closed.
-
Does the channelCount attribute support a value greater than 2? w3c/mediacapture-main#1021.
-
-
3 issues received 13 new comments.
-
What is the purpose of requiring a successful gUM call before enumerateDevices? w3c/mediacapture-main#1019 (6 comments by @guidou, @jan-ivar, @youennf)
-
What is the order of events being track clones? w3c/mediacapture-main#1020 (5 comments by @eladalon1983, @youennf)
-
Does the channelCount attribute support a value greater than 2? w3c/mediacapture-main#1021 (2 comments by @blogwy, @bradisbell)
-
w3c/webrtc-extensions
-
1 issue opened.
-
Feature request: Add event for CSRC change w3c/webrtc-extensions#230, by @koumiGoogle.
-
-
3 issues received 17 new comments.
-
Feature request: Add event for CSRC change w3c/webrtc-extensions#230 (9 comments by @dontcallmedom-bot, @guidou, @henbos, @jan-ivar, @koumiGoogle, @taylor-b)
-
Post-Quantum Crypto (PQC) support in WebRTC w3c/webrtc-extensions#207 (4 comments by @alvestrand, @Frosne, @maciejkra)
-
receiver.hardwareAcceleration attribute instead of disableHardware[En|De]coding() static method w3c/webrtc-extensions#229 (4 comments by @dontcallmedom-bot, @henbos, @jan-ivar)
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 19 new comments.
-
Auto-pause for Captured Surface Switching (2nd edition) w3c/mediacapture-screen-share-extensions#15 (19 comments by @eladalon1983, @jan-ivar, @tovepet, @youennf)
-
w3c/mediacapture-screen-share
-
1 issue opened.
-
Should screen capture tracks expose deviceId? w3c/mediacapture-screen-share#308, by @youennf.
-
-
2 issues closed.
-
Should we have a screenshare extension spec? w3c/mediacapture-screen-share#297.
-
Spec should be more explicit about exposure of deviceId w3c/mediacapture-screen-share#306.
-
-
3 issues received 15 new comments.
-
Should screen capture tracks expose deviceId? w3c/mediacapture-screen-share#308 (12 comments by @eladalon1983, @jan-ivar, @youennf)
-
Spec should be more explicit about exposure of deviceId w3c/mediacapture-screen-share#306 (2 comments by @eladalon1983, @jan-ivar)
-
Should we have a screenshare extension spec? w3c/mediacapture-screen-share#297 (1 comment by @jan-ivar)
-
w3c/mediacapture-surface-control
-
1 issue opened.
-
Consideration of proposal to support zoom in/out w3c/mediacapture-surface-control#40, by @eladalon1983.
-
-
2 issues closed.
-
Consideration of proposal to join captureWheel() and setZoomLevel() w3c/mediacapture-surface-control#24.
-
Consider limiting element types w3c/mediacapture-surface-control#28.
-
-
12 issues received 30 new comments.
-
Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? w3c/mediacapture-surface-control#45 (11 comments by @eladalon1983, @jan-ivar)
-
Address click-jacking concerns w3c/mediacapture-surface-control#41 (7 comments by @eladalon1983, @jan-ivar)
-
Is it important for capture control to keep captured tab from knowing it is captured? w3c/mediacapture-surface-control#42 (2 comments by @eladalon1983)
-
Consider dropping permission for captured surface control APIs w3c/mediacapture-surface-control#48 (2 comments by @eladalon1983)
-
Consideration of proposal to join captureWheel() and setZoomLevel() w3c/mediacapture-surface-control#24 (1 comment by @eladalon1983)
-
Consideration of proposal to support zoom in/out w3c/mediacapture-surface-control#40 (1 comment by @eladalon1983)
-
Supporting zoom via gesture forwarding w3c/mediacapture-surface-control#43 (1 comment by @eladalon1983)
-
Is setting a specific zoom level part of the MVP? w3c/mediacapture-surface-control#44 (1 comment by @eladalon1983)
-
How capturer web applications can know whether forwarding is working/useful w3c/mediacapture-surface-control#46 (1 comment by @eladalon1983)
-
Should a web page allow to select specific types of event to be forwarded and not others w3c/mediacapture-surface-control#47 (1 comment by @eladalon1983)
-
w3c/webrtc-stats
-
1 issue opened.
-
Update definitions of corruption detection probabilities to match IETF standard w3c/webrtc-stats#790, by @sprangerik.
-
-
1 issue closed.
-
Add definitions of corruption detection measurement statistics w3c/webrtc-stats#787.
-
-
1 pull request merged.
-
Add definitions of corruption detection measurements w3c/webrtc-stats#788.
-
-
1 pull request received 10 new comments.
-
Add definitions of corruption detection measurements w3c/webrtc-stats#788 (10 comments by @alvestrand, @henbos, @jan-ivar, @sprangerik, @youennf)
-
w3c/mst-content-hint
-
1 issue opened.
-
Should the spec provide guideline on the default degradation preference to use for capture tracks? w3c/mst-content-hint#60, by @youennf.
-
-
1 issue received 2 new comments.
-
Should the spec provide guideline on the default degradation preference to use for capture tracks? w3c/mst-content-hint#60 (2 comments by @alvestrand, @youennf)
-
TR publications
-
5 documents published.
-
WebRTC: Real-Time Communication in Browsers published as a Recommendation. History of WebRTC: Real-Time Communication in Browsers
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
MediaStreamTrack Content Hints published as a Working Draft. History of MediaStreamTrack Content Hints
-
Viewport Capture published as a Working Draft. History of Viewport Capture
-
Past meetings
-
1 meeting.
Participants
-
1 chair appointed.
-
Guido Urdaneta became a chair.
-
-
1 chair stepped down.
-
Harald Alvestrand stepped down as a chair.
-
-
1 participant left.
-
Göran Eriksson (ERICSSON) left.
-
GitHub
w3c/mediacapture-transform
-
1 issue opened.
-
MediaStreamTrackGenerator/MediaStream should buffer the current frame w3c/mediacapture-transform#114, by @jamiebuilds.
-
-
1 issue received 12 new comments.
-
We shouldn't require track transferability w3c/mediacapture-transform#113 (12 comments by @guidou, @jan-ivar, @youennf)
-
w3c/mst-content-hint
-
1 issue closed.
-
highly detailed text in video content w3c/mst-content-hint#35.
-
-
1 pull request merged.
-
Add health warning on "text" constraint w3c/mst-content-hint#56.
-
w3c/webrtc-extensions
-
3 issues opened.
-
receiver.hardwareAcceleration attribute instead of disableHardware[En|De]coding() static method w3c/webrtc-extensions#229, by @jan-ivar.
-
Allow not specifying scaleResolutionDownTo if encoding is inactive w3c/webrtc-extensions#227, by @henbos.
-
Editorial: Update the RTCRtpEncodingParameters non-normative section to talk about video too w3c/webrtc-extensions#226, by @henbos.
-
-
2 issues closed.
-
Allow not specifying scaleResolutionDownTo if encoding is inactive w3c/webrtc-extensions#227.
-
ReSpec errors from duplicate definitions of RTCIceCandidatePair w3c/webrtc-extensions#217.
-
-
3 issues received 6 new comments.
-
receiver.hardwareAcceleration attribute instead of disableHardware[En|De]coding() static method w3c/webrtc-extensions#229 (3 comments by @aboba, @fippo, @henbos)
-
ReSpec errors from duplicate definitions of RTCIceCandidatePair w3c/webrtc-extensions#217 (1 comment by @dontcallmedom)
-
-
1 pull request opened.
-
Don't require specifying scaleResolutionDownTo on inactive encodings w3c/webrtc-extensions#228, by @henbos.
-
-
3 pull requests merged.
-
Move transferable data channels to main spec w3c/webrtc-extensions#220.
-
Don't require specifying scaleResolutionDownTo on inactive encodings w3c/webrtc-extensions#228.
-
Correct a typo in sample code w3c/webrtc-extensions#225.
-
w3c/mediacapture-record
-
1 issue closed.
-
MediaRecorder BlobEvent timecode clarification w3c/mediacapture-record#222.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Update https://w3c.github.io/mediacapture-record/#dom-blobeventinit-timecode. w3c/mediacapture-record#223.
-
w3c/mediacapture-extensions
-
2 issues opened.
-
Reduce scope of MediaStreamTrack transfer to DedicatedWorker for now w3c/mediacapture-extensions#158, by @jan-ivar.
-
Background Blur: Which webcams support this feature? w3c/mediacapture-extensions#157, by @bluelemonade.
-
-
1 issue received 1 new comment.
-
[Explainer] Proposal for exposing the state of video effects on a MediaStreamTrack from camera capture w3c/mediacapture-extensions#155 (1 comment by @youennf)
-
-
1 pull request merged.
-
Capture, receive, and RTP timestamp concept definitions & normative requirements for gUM/gDM w3c/mediacapture-extensions#156.
-
-
1 pull request received 36 new comments.
-
Capture, receive, and RTP timestamp concept definitions & normative requirements for gUM/gDM w3c/mediacapture-extensions#156 (36 comments by @aboba, @dontcallmedom, @guidou, @handellm, @happylinks, @henbos, @jan-ivar, @padenot, @youennf)
-
w3c/mediacapture-screen-share-extensions
-
3 issues opened.
-
Option for getDisplayMedia to always return an audio track w3c/mediacapture-screen-share-extensions#17, by @tovepet.
-
Cross-Type Surface Switching w3c/mediacapture-screen-share-extensions#16, by @tovepet.
-
Auto-pause for Captured Surface Switching (2nd edition) w3c/mediacapture-screen-share-extensions#15, by @tovepet.
-
-
1 issue closed.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4.
-
-
4 issues received 57 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (32 comments by @dontcallmedom, @eladalon1983, @jan-ivar, @tovepet, @youennf)
-
Auto-pause for Captured Surface Switching (2nd edition) w3c/mediacapture-screen-share-extensions#15 (23 comments by @eladalon1983, @jan-ivar, @tovepet, @youennf)
-
Option for getDisplayMedia to always return an audio track w3c/mediacapture-screen-share-extensions#17 (1 comment by @eladalon1983)
-
Cross-Type Surface Switching w3c/mediacapture-screen-share-extensions#16 (1 comment by @eladalon1983)
-
w3c/webrtc-pc
-
5 issues opened.
-
Spec says to send black frames for ended tracks w3c/webrtc-pc#3014, by @jan-ivar.
-
Should this repo have a package-lock.json file? w3c/webrtc-pc#3012, by @alvestrand.
-
Remote track.getSettings().channelCount w3c/webrtc-pc#3011, by @henbos.
-
Opus mono/stereo and remote track channelCount w3c/webrtc-pc#3010, by @henbos.
-
Align spec /w codec direction decision w3c/webrtc-pc#3006, by @henbos.
-
-
9 issues closed.
-
Should this repo have a package-lock.json file? w3c/webrtc-pc#3012.
-
Fix ICE server URL querystring validation w3c/webrtc-pc#2912.
-
Publish Recommendation with Proposed Amendments w3c/webrtc-pc#3001.
-
RTCStats::timestamp discrepancy between webrtc-stats and webrtc-pc w3c/webrtc-pc#3004.
-
setCodecPreferences vs unidirectional codecs w3c/webrtc-pc#2888.
-
codec input to setParameters shouldn't be validated by preferred receive codecs w3c/webrtc-pc#2989.
-
setCodecPreferences, sendonly codecs and dummy codecs w3c/webrtc-pc#2937.
-
If a preferred codec is filtered out, does it still get assigned a PT? w3c/webrtc-pc#2938.
-
Proposing setCodecPreferences to deal with both send and recv codecs w3c/webrtc-pc#2939.
-
-
12 issues received 36 new comments.
-
Spec says to send black frames for ended tracks w3c/webrtc-pc#3014 (2 comments by @jan-ivar, @youennf)
-
Applying a remote offer with unsupported codecs results in stale transceiver w3c/webrtc-pc#2927 (2 comments by @henbos)
-
Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel w3c/webrtc-pc#2931 (1 comment by @gunnarhm)
-
codec input to setParameters shouldn't be validated by preferred receive codecs w3c/webrtc-pc#2989 (1 comment by @henbos)
-
If a preferred codec is filtered out, does it still get assigned a PT? w3c/webrtc-pc#2938 (1 comment by @henbos)
-
Proposing setCodecPreferences to deal with both send and recv codecs w3c/webrtc-pc#2939 (1 comment by @henbos)
-
4 pull requests opened.
-
Upgrade jsep-mapper code w3c/webrtc-pc#3013, by @dontcallmedom.
-
Demote PR 2926 as candidate instead of proposed w3c/webrtc-pc#3009, by @dontcallmedom.
-
Fix markup id for amendment 50 w3c/webrtc-pc#3008, by @dontcallmedom.
-
Update copyright links w3c/webrtc-pc#3007, by @deniak.
-
-
7 pull requests merged.
-
Upgrade jsep-mapper code w3c/webrtc-pc#3013.
-
Reject ICE servers with an authority component or / w3c/webrtc-pc#2998.
-
Complete ice server url validation w3c/webrtc-pc#2996.
-
Demote PR 2926 as candidate instead of proposed w3c/webrtc-pc#3009.
-
Support proposed amendments w3c/webrtc-pc#3002.
-
Fix markup id for amendment 50 w3c/webrtc-pc#3008.
-
Fix timestamp definition to align with webrtc-stats w3c/webrtc-pc#3005.
-
-
1 pull request closed.
-
Update copyright links w3c/webrtc-pc#3007.
-
-
4 pull requests received 9 new comments.
-
Reject ICE servers with an authority component or / w3c/webrtc-pc#2998 (6 comments by @dontcallmedom, @henbos, @jan-ivar)
-
w3c/mediacapture-surface-control
-
13 issues opened.
-
Address click-jacking concerns w3c/mediacapture-surface-control#41, by @jan-ivar.
-
Is it important for capture control to keep captured tab from knowing it is captured? w3c/mediacapture-surface-control#42, by @youennf.
-
Supporting zoom via gesture forwarding w3c/mediacapture-surface-control#43, by @youennf.
-
Is setting a specific zoom level part of the MVP? w3c/mediacapture-surface-control#44, by @youennf.
-
Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? w3c/mediacapture-surface-control#45, by @youennf.
-
How capturer web applications can know whether forwarding is working/useful w3c/mediacapture-surface-control#46, by @youennf.
-
Should a web page allow to select specific types of event to be forwarded and not others w3c/mediacapture-surface-control#47, by @youennf.
-
Dugongi's origin trial feedback w3c/mediacapture-surface-control#36, by @rallu.
-
Consider dropping permission for captured surface control APIs w3c/mediacapture-surface-control#48, by @jan-ivar.
-
Tab capture control w3c/mediacapture-surface-control#49, by @youennf.
-
Consider limiting element types w3c/mediacapture-surface-control#28, by @jan-ivar.
-
Consider dropping permission and making zoomLevel an attribute w3c/mediacapture-surface-control#27, by @jan-ivar.
-
Consideration of proposal to join captureWheel() and setZoomLevel() w3c/mediacapture-surface-control#24, by @eladalon1983.
-
-
5 issues closed.
-
Should getSupportedZoomLevels() be static? w3c/mediacapture-surface-control#8.
-
Consider dropping permission and making zoomLevel an attribute w3c/mediacapture-surface-control#27.
-
Should the deltas be called deltaX/deltaY? w3c/mediacapture-surface-control#5.
-
What value should `Event.isTrusted` have? w3c/mediacapture-surface-control#1.
-
Preventing Remote Control w3c/mediacapture-surface-control#11.
-
-
14 issues received 85 new comments.
-
Consider dropping permission for captured surface control APIs w3c/mediacapture-surface-control#48 (27 comments by @eladalon1983, @jan-ivar, @steely-glint, @youennf)
-
Tab capture control w3c/mediacapture-surface-control#49 (20 comments by @eladalon1983, @guidou, @jan-ivar, @youennf)
-
Consider dropping permission and making zoomLevel an attribute w3c/mediacapture-surface-control#27 (8 comments by @eladalon1983, @jan-ivar)
-
Is it important for capture control to keep captured tab from knowing it is captured? w3c/mediacapture-surface-control#42 (7 comments by @eladalon1983, @jan-ivar, @youennf)
-
Limit setZoomLevel() to the local user w3c/mediacapture-surface-control#14 (6 comments by @eladalon1983, @jan-ivar)
-
Consider limiting element types w3c/mediacapture-surface-control#28 (5 comments by @eladalon1983, @jan-ivar)
-
Supporting zoom via gesture forwarding w3c/mediacapture-surface-control#43 (3 comments by @eladalon1983)
-
Should a web page allow to select specific types of event to be forwarded and not others w3c/mediacapture-surface-control#47 (2 comments by @eladalon1983, @youennf)
-
Should getSupportedZoomLevels() be static? w3c/mediacapture-surface-control#8 (2 comments by @eladalon1983)
-
How capturer web applications can know whether forwarding is working/useful w3c/mediacapture-surface-control#46 (1 comment by @eladalon1983)
-
Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? w3c/mediacapture-surface-control#45 (1 comment by @eladalon1983)
-
Is setting a specific zoom level part of the MVP? w3c/mediacapture-surface-control#44 (1 comment by @eladalon1983)
-
DOM Exception: no permission instead of asking for permission w3c/mediacapture-surface-control#12 (1 comment by @eladalon1983)
-
Should the deltas be called deltaX/deltaY? w3c/mediacapture-surface-control#5 (1 comment by @eladalon1983)
-
-
21 pull requests opened.
-
Explainer links to "Security and Privacy Considerations" in spec w3c/mediacapture-surface-control#39, by @eladalon1983.
-
Disallow self-capture w3c/mediacapture-surface-control#38, by @eladalon1983.
-
Remove 'extension to window' from spec w3c/mediacapture-surface-control#37, by @eladalon1983.
-
Update README.md w3c/mediacapture-surface-control#35, by @eladalon1983.
-
Rephrase captureWheel() to avoid early-exit w3c/mediacapture-surface-control#34, by @eladalon1983.
-
[WIP] Move to forwardGestures() w3c/mediacapture-surface-control#33, by @eladalon1983.
-
Add alpha on onboarding mock w3c/mediacapture-surface-control#32, by @eladalon1983.
-
Replace mock w3c/mediacapture-surface-control#31, by @eladalon1983.
-
Align the explainer with recent changes to captureWheel() and more w3c/mediacapture-surface-control#30, by @eladalon1983.
-
Editorial - "we" w3c/mediacapture-surface-control#29, by @eladalon1983.
-
More work on Privacy and Security section w3c/mediacapture-surface-control#26, by @eladalon1983.
-
Privacy and Security Considerations w3c/mediacapture-surface-control#25, by @eladalon1983.
-
Gate sZL on trusted events w3c/mediacapture-surface-control#23, by @eladalon1983.
-
Some clarifications using <ul> w3c/mediacapture-surface-control#22, by @eladalon1983.
-
Remove unnecessary checks of allowed-to-use w3c/mediacapture-surface-control#21, by @eladalon1983.
-
Replace <var> with | w3c/mediacapture-surface-control#20, by @eladalon1983.
-
Correct the forward-wheel algorithm to check permission, not request it w3c/mediacapture-surface-control#19, by @eladalon1983.
-
Remove the requirement of system focus w3c/mediacapture-surface-control#18, by @eladalon1983.
-
Rename sections for consistency w3c/mediacapture-surface-control#17, by @eladalon1983.
-
Move the definition of new internal slots into the constructor w3c/mediacapture-surface-control#16, by @eladalon1983.
-
Remove sendWheel() w3c/mediacapture-surface-control#15, by @eladalon1983.
-
-
20 pull requests merged.
-
Explainer links to "Security and Privacy Considerations" in spec w3c/mediacapture-surface-control#39.
-
Disallow self-capture w3c/mediacapture-surface-control#38.
-
Remove 'extension to window' from spec w3c/mediacapture-surface-control#37.
-
Update README.md w3c/mediacapture-surface-control#35.
-
Rephrase captureWheel() to avoid early-exit w3c/mediacapture-surface-control#34.
-
Add alpha on onboarding mock w3c/mediacapture-surface-control#32.
-
Replace mock w3c/mediacapture-surface-control#31.
-
Align the explainer with recent changes to captureWheel() and more w3c/mediacapture-surface-control#30.
-
Editorial - "we" w3c/mediacapture-surface-control#29.
-
More work on Privacy and Security section w3c/mediacapture-surface-control#26.
-
Privacy and Security Considerations w3c/mediacapture-surface-control#25.
-
Gate sZL on trusted events w3c/mediacapture-surface-control#23.
-
Some clarifications using <ul> w3c/mediacapture-surface-control#22.
-
Remove unnecessary checks of allowed-to-use w3c/mediacapture-surface-control#21.
-
Replace <var> with | w3c/mediacapture-surface-control#20.
-
Correct the forward-wheel algorithm to check permission, not request it w3c/mediacapture-surface-control#19.
-
Remove the requirement of system focus w3c/mediacapture-surface-control#18.
-
Rename sections for consistency w3c/mediacapture-surface-control#17.
-
Move the definition of new internal slots into the constructor w3c/mediacapture-surface-control#16.
-
Remove sendWheel() w3c/mediacapture-surface-control#15.
-
-
1 pull request closed.
-
Update README.md w3c/mediacapture-surface-control#6.
-
-
1 pull request reopened.
-
Update README.md w3c/mediacapture-surface-control#6, by @eladalon1983.
-
-
1 pull request received 1 new comment.
-
Privacy and Security Considerations w3c/mediacapture-surface-control#25 (1 comment by @eladalon1983)
-
w3c/mediacapture-screen-share
-
2 issues opened.
-
Suggest User Agents treat a captured tab as visible w3c/mediacapture-screen-share#307, by @jan-ivar.
-
Spec should be more explicit about exposure of deviceId w3c/mediacapture-screen-share#306, by @eladalon1983.
-
-
1 issue closed.
-
getSupportedOptions() w3c/mediacapture-screen-share#260.
-
-
3 issues received 13 new comments.
-
Spec should be more explicit about exposure of deviceId w3c/mediacapture-screen-share#306 (9 comments by @eladalon1983, @jan-ivar, @youennf)
-
Suggest User Agents treat a captured tab as visible w3c/mediacapture-screen-share#307 (3 comments by @jan-ivar, @youennf)
-
-
1 pull request received 12 new comments.
-
Added DisplaySurfaceChangeCallback w3c/mediacapture-screen-share#289 (12 comments by @jan-ivar, @tovepet, @youennf)
-
w3c/webrtc-stats
-
1 issue opened.
-
Do not expose unknown usernameFragment to stats w3c/webrtc-stats#789, by @fippo.
-
-
1 issue received 1 new comment.
-
1 pull request received 21 new comments.
-
Add definitions of corruption detection measurements w3c/webrtc-stats#788 (21 comments by @henbos, @jan-ivar, @sprangerik, @youennf)
-
w3c/webrtc-rtptransport
-
2 issues opened.
-
Per-packet notifications are mandatory, this is not ideal for context switching w3c/webrtc-rtptransport#78, by @henbos.
-
API creates per-packet temporary objects, this is not ideal for GC w3c/webrtc-rtptransport#77, by @henbos.
-
-
1 issue closed.
-
RTCRtpSender.replaceSendStreams() and simulcast issues w3c/webrtc-rtptransport#64.
-
-
3 issues received 11 new comments.
-
API creates per-packet temporary objects, this is not ideal for GC w3c/webrtc-rtptransport#77 (7 comments by @fippo, @henbos)
-
Per-packet notifications are mandatory, this is not ideal for context switching w3c/webrtc-rtptransport#78 (3 comments by @henbos)
-
RTCRtpSender.replaceSendStreams() and simulcast issues w3c/webrtc-rtptransport#64 (1 comment by @Orphis)
-
-
1 pull request opened.
-
Do MID-level stuff instead of RID-level stuff w3c/webrtc-rtptransport#79, by @pthatcher.
-
-
1 pull request merged.
-
Do MID-level stuff instead of RID-level stuff w3c/webrtc-rtptransport#79.
-
-
1 pull request closed.
-
Make RTCRtpSendStream per mid, add rid to RTCRtpPacket/Init w3c/webrtc-rtptransport#65.
-
-
3 pull requests received 4 new comments.
-
Create RTCRtpTransportProcessor and move high freq fields there w3c/webrtc-rtptransport#68 (2 comments by @henbos, @Orphis)
-
Make RTCRtpSendStream per mid, add rid to RTCRtpPacket/Init w3c/webrtc-rtptransport#65 (1 comment by @Orphis)
-
w3c/mediacapture-region
-
1 pull request opened.
-
Editorial: s/third party/third-party w3c/mediacapture-region#85, by @eladalon1983.
-
-
1 pull request merged.
-
Editorial: s/third party/third-party w3c/mediacapture-region#85.
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Frame packetization w3c/webrtc-encoded-transform#233, by @AfonsoVilalonga.
-
-
1 issue closed.
-
Frame packetization w3c/webrtc-encoded-transform#233.
-
-
1 issue received 3 new comments.
w3c/mediacapture-image
-
1 issue opened.
-
Real-Time Access to Camera Properties in Media Capture API w3c/mediacapture-image#309, by @AkiSakurai.
-
-
1 issue received 1 new comment.
w3c/mediacapture-output
-
1 issue opened.
-
Implicit consent via getUserMedia should allow access to non-miked speakers w3c/mediacapture-output#147, by @guidou.
-
w3c/mediacapture-main
-
4 issues opened.
-
What is the purpose of requiring a successful gUM call before enumerateDevices? w3c/mediacapture-main#1019, by @guidou.
-
Questionable spec language: "MUST attempt" w3c/mediacapture-main#1018, by @eladalon1983.
-
applyConstraints() could be more useful w3c/mediacapture-main#1017, by @eladalon1983.
-
Truncated sentence in applyConstraints() w3c/mediacapture-main#1016, by @eladalon1983.
-
-
2 issues received 3 new comments.
-
Truncated sentence in applyConstraints() w3c/mediacapture-main#1016 (2 comments by @eehakkin, @eladalon1983)
-
-
1 pull request merged.
-
Define MediaStreamTrack.[[Restrictable]] w3c/mediacapture-main#1015.
-
w3c/mediacapture-viewport
-
1 issue received 1 new comment.
-
Stop referencing DisplayMediaStreamConstraints dictionary w3c/mediacapture-viewport#21 (1 comment by @eladalon1983)
-
-
1 pull request opened.
-
Introduce ViewportMediaStreamOptions w3c/mediacapture-viewport#32, by @eladalon1983.
-
-
1 pull request merged.
-
Set [Restrictable] on the video track w3c/mediacapture-viewport#31.
-
TR publications
-
1 document published.
-
Viewport Capture published as a Working Draft. History of Viewport Capture
-
Past meetings
-
3 meetings.
Participants
-
3 participants joined.
-
Sunggook Chue (Microsoft Corporation) joined.
-
Konrad Hofbauer (Google LLC) joined.
-
Jason Thomas (Datadog) joined.
-
GitHub
w3c/webrtc-rtptransport
-
3 issues opened.
-
How does RTCRtpTranport(Processor) work with RTCRtpSendStream/RTCRtpReceiveStream? w3c/webrtc-rtptransport#71, by @youennf.
-
Should RTCRtpTransport(Processor) use event handlers for packet notifications? w3c/webrtc-rtptransport#70, by @youennf.
-
How to (poly)fill out customPeerConnectionWithRtpSender() ? w3c/webrtc-rtptransport#69, by @steely-glint.
-
-
1 issue closed.
-
How to (poly)fill out customPeerConnectionWithRtpSender() ? w3c/webrtc-rtptransport#69.
-
-
2 issues received 4 new comments.
-
How to (poly)fill out customPeerConnectionWithRtpSender() ? w3c/webrtc-rtptransport#69 (2 comments by @alvestrand, @steely-glint)
-
Should RTCRtpTransport(Processor) use event handlers for packet notifications? w3c/webrtc-rtptransport#70 (2 comments by @youennf)
-
-
5 pull requests opened.
-
Update author list w3c/webrtc-rtptransport#76, by @aboba.
-
Update README.md w3c/webrtc-rtptransport#75, by @aboba.
-
Create index.html w3c/webrtc-rtptransport#74, by @aboba.
-
Copy api-outline.md content to Bikeshed document w3c/webrtc-rtptransport#73, by @Orphis.
-
Delete examples in explainer.md w3c/webrtc-rtptransport#72, by @aboba.
-
-
5 pull requests merged.
-
Update author list w3c/webrtc-rtptransport#76.
-
Update README.md w3c/webrtc-rtptransport#75.
-
Create index.html w3c/webrtc-rtptransport#74.
-
Copy api-outline.md content to Bikeshed document w3c/webrtc-rtptransport#73.
-
Delete examples in explainer.md w3c/webrtc-rtptransport#72.
-
-
2 pull requests received 15 new comments.
-
Copy api-outline.md content to Bikeshed document w3c/webrtc-rtptransport#73 (8 comments by @aboba, @Orphis)
-
Create RTCRtpTransportProcessor and move high freq fields there w3c/webrtc-rtptransport#68 (7 comments by @Orphis, @youennf)
-
w3c/mediacapture-transform
-
1 issue opened.
-
We shouldn't require track transferability w3c/mediacapture-transform#113, by @guidou.
-
-
6 issues received 23 new comments.
-
We shouldn't require track transferability w3c/mediacapture-transform#113 (13 comments by @guidou, @jan-ivar, @youennf)
-
What is the impact of timestamp for video frames enqueued in VideoTrackGenerator? w3c/mediacapture-transform#96 (5 comments by @aboba, @dontcallmedom-bot, @handellm, @steely-glint, @youennf)
-
What is the timestamp value of the VideoFrame/AudioData from a remote track? w3c/mediacapture-transform#87 (2 comments by @dontcallmedom-bot, @youennf)
-
Playback and synchronization of MediaStreamTracks created by VideoTrack Generator w3c/mediacapture-transform#86 (1 comment by @dontcallmedom-bot)
-
Expectations/requirements for VideoFrame and AudioData timestamps w3c/mediacapture-transform#80 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Add interactions with capture/presentation/receive/RTP timestamps w3c/mediacapture-transform#112, by @handellm.
-
w3c/mediacapture-output
-
2 issues opened.
-
Spec should define what the empty string (aka default device) means? w3c/mediacapture-output#146, by @youennf.
-
Missing tasks in parallel steps in Audio Output Devices API w3c/mediacapture-output#145, by @dontcallmedom-bot.
-
-
2 issues received 2 new comments.
-
Set Preferred (default) Audio Output Device in MediaDevices w3c/mediacapture-output#141 (1 comment by @youennf)
-
The first "audiooutput" `MediaDeviceInfo` returned from `enumerateDevices()` is not the default device when the default device is not exposed w3c/mediacapture-output#133 (1 comment by @youennf)
-
w3c/mediacapture-record
-
2 issues received 4 new comments.
-
MediaRecorder BlobEvent timecode clarification w3c/mediacapture-record#222 (3 comments by @alvestrand, @handellm)
-
-
1 pull request opened.
-
Update https://w3c.github.io/mediacapture-record/#dom-blobeventinit-timecode. w3c/mediacapture-record#223, by @handellm.
-
-
1 pull request received 7 new comments.
-
Update https://w3c.github.io/mediacapture-record/#dom-blobeventinit-timecode. w3c/mediacapture-record#223 (7 comments by @alvestrand, @bradisbell, @handellm, @jan-ivar, @Pehrsons)
-
w3c/mediacapture-extensions
-
1 issue opened.
-
[Explainer] Proposal for exposing the state of video effects on a MediaStreamTrack from camera capture w3c/mediacapture-extensions#155, by @markafoltz.
-
-
1 issue closed.
-
Solve user agent camera/microphone double-mute w3c/mediacapture-extensions#39.
-
-
3 issues received 4 new comments.
-
[Explainer] Proposal for exposing the state of video effects on a MediaStreamTrack from camera capture w3c/mediacapture-extensions#155 (2 comments by @markafoltz)
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (1 comment by @swapcspotsee)
-
Solve user agent camera/microphone double-mute w3c/mediacapture-extensions#39 (1 comment by @jan-ivar)
-
-
1 pull request opened.
-
Capture, receive, and RTP timestamp concept definitions & normative requirements for gUM/gDM w3c/mediacapture-extensions#156, by @handellm.
-
-
1 pull request received 16 new comments.
-
Capture, receive, and RTP timestamp concept definitions & normative requirements for gUM/gDM w3c/mediacapture-extensions#156 (16 comments by @aboba, @handellm, @jan-ivar)
-
w3c/mediacapture-viewport
-
1 issue opened.
-
Missing tasks in parallel steps in Viewport Capture w3c/mediacapture-viewport#25, by @dontcallmedom-bot.
-
-
6 pull requests opened.
-
Set [Restrictable] on the video track w3c/mediacapture-viewport#31, by @eladalon1983.
-
[=navigable/active document=] w3c/mediacapture-viewport#30, by @eladalon1983.
-
Fix [=nested browsing context=] w3c/mediacapture-viewport#29, by @eladalon1983.
-
Fix [=default allowlist=] w3c/mediacapture-viewport#28, by @eladalon1983.
-
Fix [=active document=] w3c/mediacapture-viewport#27, by @eladalon1983.
-
s/...Constraints/...Options w3c/mediacapture-viewport#26, by @eladalon1983.
-
-
5 pull requests merged.
-
[=navigable/active document=] w3c/mediacapture-viewport#30.
-
Fix [=nested browsing context=] w3c/mediacapture-viewport#29.
-
Fix [=default allowlist=] w3c/mediacapture-viewport#28.
-
Fix [=active document=] w3c/mediacapture-viewport#27.
-
s/...Constraints/...Options w3c/mediacapture-viewport#26.
-
-
5 pull requests received 13 new comments.
-
Fix [=nested browsing context=] w3c/mediacapture-viewport#29 (4 comments by @dontcallmedom, @eladalon1983)
-
Set [Restrictable] on the video track w3c/mediacapture-viewport#31 (3 comments by @eladalon1983, @youennf)
w3c/mediacapture-main
-
2 issues opened.
-
`beforeunload` prompt should display for active Media Capture sessions w3c/mediacapture-main#1013, by @thexeos.
-
Missing tasks in parallel steps in Media Capture and Streams w3c/mediacapture-main#1012, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.
-
`beforeunload` prompt should display for active Media Capture sessions w3c/mediacapture-main#1013 (1 comment by @youennf)
-
-
2 pull requests opened.
-
Define MediaStreamTrack.[[Restrictable]] w3c/mediacapture-main#1015, by @eladalon1983.
-
Update to latest ReSpec version 35.1.2 w3c/mediacapture-main#1014, by @dontcallmedom.
-
-
1 pull request merged.
-
Update to latest ReSpec version 35.1.2 w3c/mediacapture-main#1014.
-
-
1 pull request received 1 new comment.
w3c/mst-content-hint
-
1 issue received 1 new comment.
w3c/mediacapture-screen-share-extensions
-
1 issue received 3 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (3 comments by @tovepet, @youennf)
-
w3c/webrtc-extensions
-
1 issue opened.
-
What happens if scaleTo: {360p, 720p} and frame is 360 w3c/webrtc-extensions#222, by @henbos.
-
-
2 issues closed.
-
What happens if scaleTo: {360p, 720p} and frame is 360 w3c/webrtc-extensions#222.
-
RTCRtpEncodingParameters: scaleResolutionDownTo w3c/webrtc-extensions#159.
-
-
4 issues received 14 new comments.
-
What happens if scaleTo: {360p, 720p} and frame is 360 w3c/webrtc-extensions#222 (7 comments by @henbos, @jan-ivar)
-
Add API to control encode complexity w3c/webrtc-extensions#191 (5 comments by @aboba, @sprangerik, @ssilkin)
-
ICE improvements: send and prevent ICE check over a candidate pair w3c/webrtc-extensions#209 (1 comment by @dontcallmedom-bot)
-
-
3 pull requests opened.
-
Correct a typo in sample code w3c/webrtc-extensions#225, by @chun137.
-
Add WebRTC-specific interactions with capture/receive/RTP timestamps w3c/webrtc-extensions#224, by @handellm.
-
nit: r/are/MUST be downscaled w3c/webrtc-extensions#223, by @henbos.
-
-
2 pull requests merged.
-
nit: r/are/MUST be downscaled w3c/webrtc-extensions#223.
-
Add scaleResolutionDownTo to RTCRtpEncodingParameters w3c/webrtc-extensions#221.
-
-
3 pull requests received 22 new comments.
-
Add scaleResolutionDownTo to RTCRtpEncodingParameters w3c/webrtc-extensions#221 (20 comments by @henbos, @jan-ivar)
-
w3c/webrtc-stats
-
1 issue opened.
-
Add definitions of corruption detection measurement statistics w3c/webrtc-stats#787, by @sprangerik.
-
-
1 pull request opened.
-
Add definitions of corruption detection measurements w3c/webrtc-stats#788, by @sprangerik.
-
-
1 pull request received 5 new comments.
-
Add definitions of corruption detection measurements w3c/webrtc-stats#788 (5 comments by @alvestrand, @handellm, @jan-ivar, @Orphis, @sprangerik)
-
w3c/webrtc-pc
-
4 issues opened.
-
RTCStats::timestamp discrepancy between webrtc-stats and webrtc-pc w3c/webrtc-pc#3004, by @henbos.
-
Publish Recommendation with Proposed Amendments w3c/webrtc-pc#3001, by @dontcallmedom.
-
Revert integration of URL parser for ICE servers from Recommendation text w3c/webrtc-pc#2997, by @dontcallmedom.
-
-
2 issues closed.
-
Consider merging transferable RTCDataChannel from webrtc-extensions w3c/webrtc-pc#2986.
-
receiver.getParameters().codecs is broken (regression) w3c/webrtc-pc#2956.
-
-
5 issues received 16 new comments.
-
Revert integration of URL parser for ICE servers from Recommendation text w3c/webrtc-pc#2997 (9 comments by @alvestrand, @dontcallmedom)
-
`negotiationneeded` event payload should be more descriptive about what is triggering the event w3c/webrtc-pc#3003 (4 comments by @alvestrand, @fippo, @jpsantosbh)
-
Publish Recommendation with Proposed Amendments w3c/webrtc-pc#3001 (1 comment by @dontcallmedom-bot)
-
codec input to setParameters shouldn't be validated by preferred receive codecs w3c/webrtc-pc#2989 (1 comment by @docfaraday)
-
Simulcast: Implementations do not fail (and that seems good) w3c/webrtc-pc#2762 (1 comment by @dontcallmedom)
-
-
7 pull requests opened.
-
Fix timestamp definition to align with webrtc-stats w3c/webrtc-pc#3005, by @henbos.
-
Support proposed amendments w3c/webrtc-pc#3002, by @dontcallmedom.
-
Clarify that stopping of sending and receiving happens in parallel w3c/webrtc-pc#3000, by @jan-ivar.
-
Revert "Merge pull request #2935 from w3c/redefine-codecs" w3c/webrtc-pc#2999, by @jan-ivar.
-
Reject ICE servers with an authority component or / w3c/webrtc-pc#2998, by @dontcallmedom.
-
Complete ice server url validation w3c/webrtc-pc#2996, by @dontcallmedom.
-
Improve amendment management w3c/webrtc-pc#2995, by @dontcallmedom.
-
-
4 pull requests merged.
-
Make data channels transferable to DedicatedWorker w3c/webrtc-pc#2988.
-
Revert "Merge pull request #2935 from w3c/redefine-codecs" w3c/webrtc-pc#2999.
-
Clarify that stopping of sending and receiving happens in parallel w3c/webrtc-pc#3000.
-
Improve amendment management w3c/webrtc-pc#2995.
-
-
9 pull requests received 22 new comments.
-
Reject ICE servers with an authority component or / w3c/webrtc-pc#2998 (5 comments by @alvestrand, @dontcallmedom)
-
Revert "Merge pull request #2935 from w3c/redefine-codecs" w3c/webrtc-pc#2999 (3 comments by @alvestrand, @jan-ivar)
-
Fix timestamp definition to align with webrtc-stats w3c/webrtc-pc#3005 (2 comments by @henbos, @jan-ivar)
-
Clarify that stopping of sending and receiving happens in parallel w3c/webrtc-pc#3000 (1 comment by @alvestrand)
-
Merge RTCRtpEncodingParameters.codec from webrtc-extensions w3c/webrtc-pc#2985 (1 comment by @jan-ivar)
w3c/mediacapture-fromelement
-
1 issue received 1 new comment.
w3c/mediacapture-surface-control
-
1 issue opened.
-
Limit setZoomLevel() to the local user w3c/mediacapture-surface-control#14, by @eladalon1983.
-
-
1 issue reopened.
-
Extend API to Support PageUp/PageDown Button Press w3c/mediacapture-surface-control#10, by @eladalon1983.
-
-
1 issue received 2 new comments.
-
Extend API to Support PageUp/PageDown Button Press w3c/mediacapture-surface-control#10 (2 comments by @eladalon1983, @guidou)
-
w3c/webrtc-encoded-transform
-
1 issue received 3 new comments.
-
No transfer steps defined for RTCEncodedAudioFrame and RTCEncodedVideoFrame w3c/webrtc-encoded-transform#231 (3 comments by @guidou, @jan-ivar, @youennf)
-
w3c/mediacapture-region
-
1 issue opened.
-
Missing tasks in parallel steps in Region Capture w3c/mediacapture-region#84, by @dontcallmedom-bot.
-
w3c/mediacapture-handle
-
1 issue opened.
-
[mediacapture-handle-actions] Missing tasks in parallel steps in The Capture-Handle Actions Mechanism w3c/mediacapture-handle#77, by @dontcallmedom-bot.
-
w3c/mediacapture-image
-
1 issue opened.
-
Missing tasks in parallel steps in MediaStream Image Capture w3c/mediacapture-image#308, by @dontcallmedom-bot.
-
Lifecycle
-
1 charter started.
-
Chartered until 30 September 2026.
-
TR publications
-
2 documents published.
-
Scalable Video Coding (SVC) Extension for WebRTC published as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
MediaStreamTrack Content Hints published as a Working Draft. History of MediaStreamTrack Content Hints
-
Past meetings
-
1 meeting.
GitHub
w3c/webrtc-pc
-
4 issues opened.
-
codec input to setParameters shouldn't be validated by preferred receive codecs w3c/webrtc-pc#2989, by @jan-ivar.
-
RTCRtpParameters.codec matching is probably too strict w3c/webrtc-pc#2987, by @docfaraday.
-
Consider merging transferable RTCDataChannel from webrtc-extensions w3c/webrtc-pc#2986, by @tguilbert-google.
-
Unspecified whether the data channel error event fires from SCTP ABORT w3c/webrtc-pc#2984, by @jan-ivar.
-
-
3 issues received 23 new comments.
-
RTCRtpParameters.codec matching is probably too strict w3c/webrtc-pc#2987 (14 comments by @aboba, @alvestrand, @docfaraday, @dontcallmedom-bot, @fippo, @jan-ivar, @Orphis)
-
Consider merging transferable RTCDataChannel from webrtc-extensions w3c/webrtc-pc#2986 (8 comments by @alvestrand, @dontcallmedom, @tguilbert-google, @youennf)
-
codec input to setParameters shouldn't be validated by preferred receive codecs w3c/webrtc-pc#2989 (1 comment by @alvestrand)
-
-
7 pull requests opened.
-
Improve description of amendment 36 w3c/webrtc-pc#2994, by @dontcallmedom.
-
Improve and complete description of amendments 16, 18, 29, 49 w3c/webrtc-pc#2993, by @dontcallmedom.
-
Fix description of amendments 23, 31, 47 w3c/webrtc-pc#2992, by @dontcallmedom.
-
Don't validate codec input to setParameters by preferred receive codecs w3c/webrtc-pc#2991, by @jan-ivar.
-
Reference the codec parameter in algorithms. w3c/webrtc-pc#2990, by @jan-ivar.
-
Make data channels transferable to DedicatedWorker w3c/webrtc-pc#2988, by @dontcallmedom.
-
Merge RTCRtpEncodingParameters.codec from webrtc-extensions w3c/webrtc-pc#2985, by @Orphis.
-
-
6 pull requests merged.
-
Improve description of amendment 36 w3c/webrtc-pc#2994.
-
Improve and complete description of amendments 16, 18, 29, 49 w3c/webrtc-pc#2993.
-
Fix description of amendments 23, 31, 47 w3c/webrtc-pc#2992.
-
Reference the codec parameter in algorithms. w3c/webrtc-pc#2990.
-
Merge RTCRtpEncodingParameters.codec from webrtc-extensions w3c/webrtc-pc#2985.
-
Update to ReSpec version 35.1.1 w3c/webrtc-pc#2982.
-
-
2 pull requests received 4 new comments.
-
Merge RTCRtpEncodingParameters.codec from webrtc-extensions w3c/webrtc-pc#2985 (3 comments by @jan-ivar)
-
Don't validate codec input to setParameters by preferred receive codecs w3c/webrtc-pc#2991 (1 comment by @jan-ivar)
-
w3c/webrtc-encoded-transform
-
3 issues opened.
-
Enum values that ignore naming conventions in WebRTC Encoded Transform w3c/webrtc-encoded-transform#232, by @dontcallmedom-bot.
-
No transfer steps defined for RTCEncodedAudioFrame and RTCEncodedVideoFrame w3c/webrtc-encoded-transform#231, by @luciaalonsomozo.
-
Clarification on "not processing video packets" requested w3c/webrtc-encoded-transform#230, by @luciaalonsomozo.
-
-
2 issues received 12 new comments.
-
Clarification on "not processing video packets" requested w3c/webrtc-encoded-transform#230 (7 comments by @alvestrand, @fippo, @guidou, @jan-ivar, @luciaalonsomozo)
-
Add use cases that require one-ended encoded streams w3c/webrtc-encoded-transform#106 (5 comments by @alvestrand, @fippo, @vitaly-castLabs)
-
-
2 pull requests closed.
-
Refactor spec to introduce media thread w3c/webrtc-encoded-transform#107.
-
Document legacy API that was removed in #64 w3c/webrtc-encoded-transform#111.
-
-
2 pull requests received 2 new comments.
-
Document legacy API that was removed in #64 w3c/webrtc-encoded-transform#111 (1 comment by @alvestrand)
w3c/webrtc-extensions
-
1 issue opened.
-
ReSpec errors from duplicate definitions of RTCIceCandidatePair w3c/webrtc-extensions#217, by @sam-vi.
-
-
1 issue closed.
-
Migrate RTCRtpEncodingParameters.codec to main spec w3c/webrtc-extensions#212.
-
-
6 issues received 11 new comments.
-
Clarify status of RTP Header Extension for Absolute Capture Time w3c/webrtc-extensions#201 (3 comments by @alvestrand, @Arctunix, @drkron)
-
RTCRtpEncodingParameters: scaleResolutionDownTo w3c/webrtc-extensions#159 (2 comments by @dontcallmedom-bot, @henbos)
-
Support ICE Continuous Gathering flag in RTCConfiguration w3c/webrtc-extensions#121 (2 comments by @alvestrand, @lgrahl)
-
Implementation commitments for transferable data channels w3c/webrtc-extensions#214 (2 comments by @Orphis, @tguilbert-google)
-
ReSpec errors from duplicate definitions of RTCIceCandidatePair w3c/webrtc-extensions#217 (1 comment by @dontcallmedom)
-
-
4 pull requests opened.
-
Add scaleResolutionDownTo to RTCRtpEncodingParameters w3c/webrtc-extensions#221, by @henbos.
-
Move transferable data channels to main spec w3c/webrtc-extensions#220, by @dontcallmedom.
-
Move RTCRtpEncodingParameters.codec to main spec w3c/webrtc-extensions#219, by @dontcallmedom.
-
Fix RTCIceCandidatePair links to suppress ambiguity warnings. w3c/webrtc-extensions#218, by @sam-vi.
-
-
1 pull request merged.
-
Move RTCRtpEncodingParameters.codec to main spec w3c/webrtc-extensions#219.
-
-
4 pull requests received 21 new comments.
-
Add scaleResolutionDownTo to RTCRtpEncodingParameters w3c/webrtc-extensions#221 (17 comments by @alvestrand, @henbos)
-
Move RTCRtpEncodingParameters.codec to main spec w3c/webrtc-extensions#219 (2 comments by @jan-ivar, @Orphis)
-
Use RTCIceCandidatePair interface in RTCIceTransport w3c/webrtc-extensions#205 (1 comment by @sam-vi)
-
w3c/mediacapture-output
-
1 issue closed.
-
Why prompt for a subset of stored speakers or speakers setSinkId already accepts? w3c/mediacapture-output#142.
-
-
2 issues received 16 new comments.
-
The first "audiooutput" `MediaDeviceInfo` returned from `enumerateDevices()` is not the default device when the default device is not exposed w3c/mediacapture-output#133 (14 comments by @dontcallmedom-bot, @guidou, @jan-ivar, @karlt)
-
Why prompt for a subset of stored speakers or speakers setSinkId already accepts? w3c/mediacapture-output#142 (2 comments by @dontcallmedom-bot, @youennf)
-
-
2 pull requests opened.
-
Mark Justin as former editor w3c/mediacapture-output#144, by @dontcallmedom.
-
Allow prompt bypass for miked speakers exposed through getUserMedia() w3c/mediacapture-output#143, by @jan-ivar.
-
-
2 pull requests merged.
-
Mark Justin as former editor w3c/mediacapture-output#144.
-
Allow prompt bypass for miked speakers exposed through getUserMedia() w3c/mediacapture-output#143.
-
-
1 pull request received 5 new comments.
-
Allow prompt bypass for miked speakers exposed through getUserMedia() w3c/mediacapture-output#143 (5 comments by @dontcallmedom-bot, @jan-ivar, @youennf)
-
w3c/mediacapture-main
-
1 issue opened.
-
Should a muted video track be allowed to deliver black frames to its sinks? w3c/mediacapture-main#1011, by @youennf.
-
-
1 issue closed.
-
(webkit|moz)getUserMedia usage and webcompat issues w3c/mediacapture-main#992.
-
-
3 issues received 3 new comments.
-
Should a muted video track be allowed to deliver black frames to its sinks? w3c/mediacapture-main#1011 (1 comment by @youennf)
-
-
1 pull request closed.
-
Define getMuteReasons() w3c/mediacapture-main#979.
-
-
1 pull request received 1 new comment.
w3c/webrtc-stats
-
1 issue closed.
-
RTCCodecStats.clockRate - media sampling rate or the codec clock rate? w3c/webrtc-stats#785.
-
-
2 issues received 4 new comments.
-
RTCCodecStats.clockRate - media sampling rate or the codec clock rate? w3c/webrtc-stats#785 (2 comments by @alvestrand, @vr000m)
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 1 new comment.
-
Want to restrict the options of the getDisplayMedia API w3c/mediacapture-screen-share-extensions#1 (1 comment by @robinma)
-
w3c/mediacapture-surface-control
-
1 issue received 1 new comment.
-
DOM Exception: no permission instead of asking for permission w3c/mediacapture-surface-control#12 (1 comment by @rallu)
-
-
1 pull request opened.
-
Add captureWheel() w3c/mediacapture-surface-control#13, by @guidou.
-
-
1 pull request merged.
-
Add captureWheel() w3c/mediacapture-surface-control#13.
-
w3c/webrtc-rtptransport
-
4 issues opened.
-
Unsignalled streams aren't needed by any existing usecase w3c/webrtc-rtptransport#66, by @tonyherre.
-
RTCRtpSender.replaceSendStreams() and simulcast issues w3c/webrtc-rtptransport#64, by @Orphis.
-
BYOB also needs fields giving the byte length w3c/webrtc-rtptransport#62, by @tonyherre.
-
Allow inserting padding into packets w3c/webrtc-rtptransport#60, by @tonyherre.
-
-
3 issues closed.
-
Unsignalled streams aren't needed by any existing usecase w3c/webrtc-rtptransport#66.
-
BYOB also needs fields giving the byte length w3c/webrtc-rtptransport#62.
-
Allow inserting padding into packets w3c/webrtc-rtptransport#60.
-
-
3 issues received 13 new comments.
-
Unsignalled streams aren't needed by any existing usecase w3c/webrtc-rtptransport#66 (7 comments by @aboba, @alvestrand, @Orphis, @pthatcher, @tonyherre)
-
RTCRtpSender.replaceSendStreams() and simulcast issues w3c/webrtc-rtptransport#64 (4 comments by @aboba, @Orphis, @pthatcher)
-
-
5 pull requests opened.
-
Create RTCRtpTransportProcessor and move high freq fields there w3c/webrtc-rtptransport#68, by @tonyherre.
-
Remove unmotivated addRtpXStreams methods w3c/webrtc-rtptransport#67, by @tonyherre.
-
Make RTCRtpSendStream per mid, add rid to RTCRtpPacket/Init w3c/webrtc-rtptransport#65, by @Orphis.
-
Add byte length fields for BYOB methods w3c/webrtc-rtptransport#63, by @tonyherre.
-
Add paddingBytes fields w3c/webrtc-rtptransport#61, by @tonyherre.
-
-
3 pull requests merged.
-
Remove unmotivated addRtpXStreams methods w3c/webrtc-rtptransport#67.
-
Add byte length fields for BYOB methods w3c/webrtc-rtptransport#63.
-
Add paddingBytes fields w3c/webrtc-rtptransport#61.
-
-
5 pull requests received 10 new comments.
-
Make RTCRtpSendStream per mid, add rid to RTCRtpPacket/Init w3c/webrtc-rtptransport#65 (3 comments by @Orphis, @pthatcher)
-
Create RTCRtpTransportProcessor and move high freq fields there w3c/webrtc-rtptransport#68 (3 comments by @alvestrand, @pthatcher, @tonyherre)
-
Add byte length fields for BYOB methods w3c/webrtc-rtptransport#63 (2 comments by @aboba, @tonyherre)
-
w3c/mediacapture-extensions
-
2 issues closed.
-
mediastream cannot handle webcam data stream in yuv pixel format correctly w3c/mediacapture-extensions#99.
-
Clarifying Transferable MediaStreamTrack Types w3c/mediacapture-extensions#154.
-
-
3 issues received 4 new comments.
-
mediastream cannot handle webcam data stream in yuv pixel format correctly w3c/mediacapture-extensions#99 (2 comments by @aboba, @guidou)
-
Clarifying Transferable MediaStreamTrack Types w3c/mediacapture-extensions#154 (1 comment by @aboba)
-
-
1 pull request closed.
-
Specify constraint echoCancellationReferenceSinkId w3c/mediacapture-extensions#32.
-
-
1 pull request received 1 new comment.
-
Specify constraint echoCancellationReferenceSinkId w3c/mediacapture-extensions#32 (1 comment by @alvestrand)
-
w3c/webrtc-priority
-
1 issue opened.
-
Migrate RTCDataChannel.priority to main spec w3c/webrtc-priority#24, by @Orphis.
-
w3c/mst-content-hint
-
1 pull request merged.
-
Improve markup of enumeration tables w3c/mst-content-hint#57.
-
TR publications
-
1 document published.
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Participants
-
2 participants joined.
-
Hu Liu (Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司）) joined.
-
Jasper Hugo (Datadog) joined.
-
-
2 organizations joined.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） joined.
-
Datadog joined.
-
-
1 organization left.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） left.
-
GitHub
w3c/webrtc-rtptransport
-
2 issues opened.
-
No signal when transport path change. w3c/webrtc-rtptransport#57, by @Philipel-WebRTC.
-
Custom BWE without pacing is not well supported. w3c/webrtc-rtptransport#56, by @Philipel-WebRTC.
-
-
2 issues received 3 new comments.
-
Make RtpTransportProcessor transferable w3c/webrtc-rtptransport#33 (2 comments by @aboba, @tonyherre)
-
RtpSendStreamInit and RtpReceiveStreamInit are not defined in explainer-use-case-1.md w3c/webrtc-rtptransport#35 (1 comment by @tonyherre)
-
-
2 pull requests opened.
-
Add use case 3 for custom NACK/RTX w3c/webrtc-rtptransport#59, by @pthatcher.
-
Cross stream and transport wide RTP/RTCP w3c/webrtc-rtptransport#58, by @Philipel-WebRTC.
-
-
1 pull request merged.
-
Add batch interfaces for reading RtpSents and RtpAcks w3c/webrtc-rtptransport#42.
-
-
2 pull requests received 3 new comments.
-
Add use case 3 for custom NACK/RTX w3c/webrtc-rtptransport#59 (2 comments by @Philipel-WebRTC, @tonyherre)
-
Add batch interfaces for reading RtpSents and RtpAcks w3c/webrtc-rtptransport#42 (1 comment by @pthatcher)
-
w3c/webrtc-charter
-
1 issue opened.
-
Representing Meetings' Transcripts and Minutes w3c/webrtc-charter#84, by @AdamSobieski.
-
-
1 issue closed.
-
Representing Meetings' Transcripts and Minutes w3c/webrtc-charter#84.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
add missing /ul, more accurate Changes summary w3c/webrtc-charter#85, by @tantek.
-
-
1 pull request merged.
-
add missing /ul, more accurate Changes summary w3c/webrtc-charter#85.
-
-
1 pull request received 1 new comment.
w3c/webrtc-encoded-transform
-
2 issues received 4 new comments.
-
Does Chromium require anything in SDP or RTP Header to make this work? w3c/webrtc-encoded-transform#37 (2 comments by @alexivaner, @fippo)
-
Generalize ScriptTransform constructor to allow main-thread processing w3c/webrtc-encoded-transform#89 (2 comments by @fippo, @jan-ivar)
-
-
2 pull requests closed.
-
Remove restriction on streams being limited to only one PC w3c/webrtc-encoded-transform#201.
-
IDL changes for setMetadata for 3.2.2 webrtc nv use case w3c/webrtc-encoded-transform#202.
-
-
2 pull requests received 2 new comments.
-
Remove restriction on streams being limited to only one PC w3c/webrtc-encoded-transform#201 (1 comment by @guidou)
-
IDL changes for setMetadata for 3.2.2 webrtc nv use case w3c/webrtc-encoded-transform#202 (1 comment by @guidou)
-
w3c/webrtc-stats
-
1 pull request merged.
-
raddr+rport can be set for peer-reflexive candidates as well w3c/webrtc-stats#783.
-
w3c/webrtc-extensions
-
1 issue closed.
-
Normative reference to googlesource.com w3c/webrtc-extensions#216.
-
-
2 issues received 2 new comments.
-
Clarify status of RTP Header Extension for Absolute Capture Time w3c/webrtc-extensions#201 (1 comment by @dontcallmedom)
-
-
1 pull request received 1 new comment.
w3c/mediacapture-extensions
-
2 issues closed.
-
Consider adding onVoiceActivity event on MediaStreamTrack for audio w3c/mediacapture-extensions#145.
-
How to select camera presets that have better power efficiency at the expense of quality? w3c/mediacapture-extensions#149.
-
-
1 pull request merged.
-
Add a powerEfficient constraint w3c/mediacapture-extensions#152.
-
-
1 pull request received 1 new comment.
w3c/mediacapture-screen-share
-
1 pull request received 1 new comment.
-
Avoid implicit task queuing with promises, to clarify setFocusBehavior w3c/mediacapture-screen-share#304 (1 comment by @alvestrand)
-
w3c/mediacapture-output
-
1 issue opened.
-
Why prompt for a subset of stored speakers or speakers setSinkId already accepts? w3c/mediacapture-output#142, by @jan-ivar.
-
w3c/mediacapture-surface-control
-
1 issue opened.
-
DOM Exception: no permission instead of asking for permission w3c/mediacapture-surface-control#12, by @vishaldialpad.
-
-
1 issue received 1 new comment.
-
DOM Exception: no permission instead of asking for permission w3c/mediacapture-surface-control#12 (1 comment by @eladalon1983)
-
w3c/webrtc-pc
-
1 pull request opened.
-
Update localDescription etc. attributes rather than just their sdp. w3c/webrtc-pc#2983, by @jan-ivar.
-
-
2 pull requests received 4 new comments.
-
Convert RTCIceCandidatePair dictionary to an interface w3c/webrtc-pc#2961 (3 comments by @jan-ivar, @sam-vi, @saschanaz)
-
Update localDescription etc. attributes rather than just their sdp. w3c/webrtc-pc#2983 (1 comment by @dontcallmedom)
-
w3c/mediacapture-transform
-
1 issue opened.
-
First timestamp generated by mediastream fails w3c/mediacapture-transform#111, by @tiuvi.
-
-
1 issue closed.
-
First timestamp generated by mediastream fails w3c/mediacapture-transform#111.
-
-
2 issues received 4 new comments.
-
First timestamp generated by mediastream fails w3c/mediacapture-transform#111 (3 comments by @guidou, @tiuvi)
-
w3c/mediacapture-main
-
1 issue received 8 new comments.
-
Get raw data from MediaStream w3c/mediacapture-main#327 (8 comments by @BlobTheKat, @bradisbell, @fippo, @James-E-A, @youennf)
-
w3c/mediacapture-record
-
1 issue received 1 new comment.
TR publications
-
4 documents published.
-
Media Capture and Streams published twice as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Screen Capture published as a Working Draft. History of Screen Capture
-
Past meetings
-
1 meeting.
GitHub
w3c/webrtc-rtptransport
-
7 issues opened.
-
Add stats on queued event drops when apps aren't keeping up with reading w3c/webrtc-rtptransport#55, by @tonyherre.
-
Controls of internal queue lengths w3c/webrtc-rtptransport#54, by @tonyherre.
-
Sending NACK/FEC is not supported w3c/webrtc-rtptransport#52, by @Philipel-WebRTC.
-
There are two `readPacketizedRtp` functions. w3c/webrtc-rtptransport#49, by @Philipel-WebRTC.
-
RtpTransport and transport re-direction w3c/webrtc-rtptransport#48, by @aboba.
-
Should `RtpSendStream` and `RtpReceiveStream` be removed? w3c/webrtc-rtptransport#47, by @Philipel-WebRTC.
-
Sequence number: constraints? w3c/webrtc-rtptransport#43, by @aboba.
-
-
3 issues closed.
-
RtpTransport should be called RTCRtpTransport w3c/webrtc-rtptransport#2.
-
Potential issues from convenience extensions w3c/webrtc-rtptransport#39.
-
BYOB interfaces to avoid ArrayBuffer churn w3c/webrtc-rtptransport#41.
-
-
13 issues received 37 new comments.
-
RtpTransport should be called RTCRtpTransport w3c/webrtc-rtptransport#2 (9 comments by @alvestrand, @dontcallmedom, @pthatcher, @tonyherre)
-
Sequence number: constraints? w3c/webrtc-rtptransport#43 (6 comments by @aboba, @algesten, @alvestrand, @Philipel-WebRTC, @tonyherre)
-
Make RtpTransportProcessor transferable w3c/webrtc-rtptransport#33 (4 comments by @tonyherre, @youennf)
-
Should `RtpSendStream` and `RtpReceiveStream` be removed? w3c/webrtc-rtptransport#47 (4 comments by @Philipel-WebRTC, @tonyherre)
-
How do the two `sendRtp` functions interact? w3c/webrtc-rtptransport#32 (4 comments by @Philipel-WebRTC, @tonyherre)
-
Custom extensions not supported w3c/webrtc-rtptransport#29 (3 comments by @alvestrand, @Philipel-WebRTC, @pthatcher)
-
RtpSendStreamInit and RtpReceiveStreamInit are not defined in explainer-use-case-1.md w3c/webrtc-rtptransport#35 (1 comment by @tonyherre)
-
Should RtpSendStream/RtpReceiveStream be transferable? w3c/webrtc-rtptransport#36 (1 comment by @Philipel-WebRTC)
-
-
6 pull requests opened.
-
Add RTC- prefix to all types w3c/webrtc-rtptransport#53, by @tonyherre.
-
Add read methods for sent RTP and acked RTP w3c/webrtc-rtptransport#51, by @pthatcher.
-
Remove associated rtxSsrc from RtpSendStream and RtpReceiveStream. w3c/webrtc-rtptransport#50, by @Philipel-WebRTC.
-
Resolve the indecisive attribute/getter on PeerConnection w3c/webrtc-rtptransport#46, by @tonyherre.
-
Merge the API into one file. w3c/webrtc-rtptransport#45, by @Philipel-WebRTC.
-
Replace ArrayBuffers with BYOB methods/AllowSharedBufferSources w3c/webrtc-rtptransport#44, by @tonyherre.
-
-
5 pull requests merged.
-
Add RTC- prefix to all types w3c/webrtc-rtptransport#53.
-
[Bikeshedding] Remove RtpPacketInit convenience extensions. w3c/webrtc-rtptransport#31.
-
Merge the API into one file. w3c/webrtc-rtptransport#45.
-
Resolve the indecisive attribute/getter on PeerConnection w3c/webrtc-rtptransport#46.
-
Replace ArrayBuffers with BYOB methods/AllowSharedBufferSources w3c/webrtc-rtptransport#44.
-
-
2 pull requests closed.
-
RTC + RtpTransport = true w3c/webrtc-rtptransport#3.
-
Add read methods for sent RTP and acked RTP w3c/webrtc-rtptransport#51.
-
-
9 pull requests received 29 new comments.
-
Add batch interfaces for reading RtpSents and RtpAcks w3c/webrtc-rtptransport#42 (11 comments by @Philipel-WebRTC, @pthatcher, @tonyherre, @youennf)
-
Resolve the indecisive attribute/getter on PeerConnection w3c/webrtc-rtptransport#46 (5 comments by @Philipel-WebRTC, @pthatcher, @tonyherre)
-
Merge the API into one file. w3c/webrtc-rtptransport#45 (3 comments by @Philipel-WebRTC, @tonyherre)
-
[Bikeshedding] Remove RtpPacketInit convenience extensions. w3c/webrtc-rtptransport#31 (3 comments by @Philipel-WebRTC, @pthatcher, @tonyherre)
-
Add read methods for sent RTP and acked RTP w3c/webrtc-rtptransport#51 (2 comments by @pthatcher, @tonyherre)
-
Remove associated rtxSsrc from RtpSendStream and RtpReceiveStream. w3c/webrtc-rtptransport#50 (1 comment by @pthatcher)
-
Replace ArrayBuffers with BYOB methods/AllowSharedBufferSources w3c/webrtc-rtptransport#44 (1 comment by @tonyherre)
-
w3c/mediacapture-extensions
-
2 issues opened.
-
Clarifying Transferable MediaStreamTrack Types w3c/mediacapture-extensions#154, by @bc-lee.
-
How to select camera presets that have better power efficiency at the expense of quality? w3c/mediacapture-extensions#149, by @youennf.
-
-
1 issue closed.
-
Spec sections are not well organised w3c/mediacapture-extensions#64.
-
-
4 issues received 5 new comments.
-
How to select camera presets that have better power efficiency at the expense of quality? w3c/mediacapture-extensions#149 (2 comments by @dontcallmedom-bot, @youennf)
-
Clarifying Transferable MediaStreamTrack Types w3c/mediacapture-extensions#154 (1 comment by @youennf)
-
Consider adding onVoiceActivity event on MediaStreamTrack for audio w3c/mediacapture-extensions#145 (1 comment by @dontcallmedom-bot)
-
-
6 pull requests opened.
-
Add MediaStreamTrack voice activity detection support. w3c/mediacapture-extensions#153, by @jianjunz.
-
Add a powerEfficient constraint w3c/mediacapture-extensions#152, by @youennf.
-
Fix broken links w3c/mediacapture-extensions#151, by @dontcallmedom.
-
Move backgroundBlur to main spec w3c/mediacapture-extensions#150, by @dontcallmedom.
-
Fix typos. w3c/mediacapture-extensions#148, by @jan-ivar.
-
Add Elad Alon to editors w3c/mediacapture-extensions#147, by @eladalon1983.
-
-
4 pull requests merged.
-
Move backgroundBlur to main spec w3c/mediacapture-extensions#150.
-
Fix broken links w3c/mediacapture-extensions#151.
-
Fix typos. w3c/mediacapture-extensions#148.
-
Add Elad Alon to editors w3c/mediacapture-extensions#147.
-
-
1 pull request closed.
-
Add MediaStreamTrack voice activity detection support. w3c/mediacapture-extensions#153.
-
-
4 pull requests received 26 new comments.
-
Add MediaStreamTrack voice activity detection support. w3c/mediacapture-extensions#153 (11 comments by @bradisbell, @guidou, @jan-ivar, @jianjunz, @youennf)
-
Add a powerEfficient constraint w3c/mediacapture-extensions#152 (8 comments by @alvestrand, @jan-ivar, @youennf)
-
Add background segmentation mask w3c/mediacapture-extensions#142 (6 comments by @alvestrand, @eehakkin, @jan-ivar)
-
w3c/mediacapture-main
-
2 issues closed.
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966.
-
repo name nit: it'd be nice if this were simply w3c/mediacapture w3c/mediacapture-main#1003.
-
-
3 issues received 3 new comments.
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966 (1 comment by @dontcallmedom-bot)
-
How to handle specs that extend MediaStreamTrack, in particular MediaStreamTrack slots? w3c/mediacapture-main#1004 (1 comment by @jan-ivar)
-
repo name nit: it'd be nice if this were simply w3c/mediacapture w3c/mediacapture-main#1003 (1 comment by @dontcallmedom)
-
-
5 pull requests opened.
-
Export the allowed required constraints for device selection definition w3c/mediacapture-main#1010, by @youennf.
-
Update to latest ReSpec version 35.1.1 w3c/mediacapture-main#1009, by @dontcallmedom.
-
Add userInsertedDevices attribute to DeviceChangeEvent w3c/mediacapture-main#1007, by @jan-ivar.
-
Import backgroundBlur from mediacapture-extensions w3c/mediacapture-main#1006, by @dontcallmedom.
-
Update to latest ReSpec version 35.1.0 w3c/mediacapture-main#1005, by @dontcallmedom.
-
-
5 pull requests merged.
-
Export the allowed required constraints for device selection definition w3c/mediacapture-main#1010.
-
Update to latest ReSpec version 35.1.1 w3c/mediacapture-main#1009.
-
Import backgroundBlur from mediacapture-extensions w3c/mediacapture-main#1006.
-
Add userInsertedDevices attribute to DeviceChangeEvent w3c/mediacapture-main#1007.
-
Update to latest ReSpec version 35.1.0 w3c/mediacapture-main#1005.
-
-
2 pull requests received 4 new comments.
-
Export the allowed required constraints for device selection definition w3c/mediacapture-main#1010 (2 comments by @dontcallmedom, @youennf)
-
Add userInsertedDevices attribute to DeviceChangeEvent w3c/mediacapture-main#1007 (2 comments by @alvestrand, @dontcallmedom-bot)
-
w3c/mediacapture-record
-
1 issue opened.
-
MediaRecorder BlobEvent timecode clarification w3c/mediacapture-record#222, by @bradisbell.
-
-
2 issues received 2 new comments.
-
1 pull request received 1 new comment.
w3c/mediacapture-screen-share
-
1 issue opened.
-
Spec relies on implicit task queuing, mixing up setFocusBehavior() timing w3c/mediacapture-screen-share#303, by @jan-ivar.
-
-
2 pull requests opened.
-
Fix a couple of links to Media Capture and Streams w3c/mediacapture-screen-share#305, by @dontcallmedom.
-
Avoid implicit task queuing with promises, to clarify setFocusBehavior w3c/mediacapture-screen-share#304, by @jan-ivar.
-
-
1 pull request merged.
-
Fix a couple of links to Media Capture and Streams w3c/mediacapture-screen-share#305.
-
-
1 pull request received 1 new comment.
-
Avoid implicit task queuing with promises, to clarify setFocusBehavior w3c/mediacapture-screen-share#304 (1 comment by @jan-ivar)
-
w3c/webrtc-pc
-
2 issues closed.
-
Write WPT to check RTCIceCandidatePair is now an interface w3c/webrtc-pc#2978.
-
RTCRtpCodecCapability is superfluous and should be deleted from the spec. w3c/webrtc-pc#2974.
-
-
3 issues received 7 new comments.
-
PC.local_description and friends - snapshot views or dynamic views? w3c/webrtc-pc#2977 (3 comments by @alvestrand, @dontcallmedom-bot, @jan-ivar)
-
RTCRtpCodecCapability is superfluous and should be deleted from the spec. w3c/webrtc-pc#2974 (3 comments by @fippo, @jan-ivar)
-
Write WPT to check RTCIceCandidatePair is now an interface w3c/webrtc-pc#2978 (1 comment by @dontcallmedom)
-
-
4 pull requests opened.
-
Update to ReSpec version 35.1.1 w3c/webrtc-pc#2982, by @dontcallmedom.
-
Add link to 'in parallel' definition w3c/webrtc-pc#2981, by @dontcallmedom.
-
Update to ReSpec version 35.1.0 w3c/webrtc-pc#2980, by @dontcallmedom.
-
Add reference to WPT update for idlharness of icecandidateapair interface w3c/webrtc-pc#2979, by @dontcallmedom.
-
-
4 pull requests merged.
-
Add link to 'in parallel' definition w3c/webrtc-pc#2981.
-
Add reference to WPT update for idlharness of icecandidateapair interface w3c/webrtc-pc#2979.
-
Collapse RTCRtpCodecCapability. w3c/webrtc-pc#2976.
-
Update to ReSpec version 35.1.0 w3c/webrtc-pc#2980.
-
-
2 pull requests received 3 new comments.
-
Separate Send/ReceiveCodecs and NegotiatedCodecs w3c/webrtc-pc#2972 (2 comments by @alvestrand, @dontcallmedom)
-
w3c/mediacapture-surface-control
-
2 issues opened.
-
Preventing Remote Control w3c/mediacapture-surface-control#11, by @guidou.
-
Extend API to Support PageUp/PageDown Button Press w3c/mediacapture-surface-control#10, by @vishaldialpad.
-
-
1 issue received 2 new comments.
-
What value should `Event.isTrusted` have? w3c/mediacapture-surface-control#1 (2 comments by @guidou)
-
w3c/webrtc-extensions
-
9 issues opened.
-
Normative reference to googlesource.com w3c/webrtc-extensions#216, by @jan-ivar.
-
captureTimestamp: RTCRtpContributingSource vs RTCRtpSynchronizationSource w3c/webrtc-extensions#215, by @dontcallmedom.
-
Implementation commitments for transferable data channels w3c/webrtc-extensions#214, by @dontcallmedom.
-
Implementation commitments on RTCEncodingOptions.keyFrame? w3c/webrtc-extensions#213, by @dontcallmedom.
-
Migrate RTCRtpEncodingParameters.codec to main spec w3c/webrtc-extensions#212, by @dontcallmedom.
-
Migrate adaptivePtime to main spec w3c/webrtc-extensions#211, by @dontcallmedom.
-
Migrate "RTP header extension control" to main spec w3c/webrtc-extensions#210, by @dontcallmedom.
-
ICE improvements: send and prevent ICE check over a candidate pair w3c/webrtc-extensions#209, by @sam-vi.
-
RTCIceTransport extensions vs webrtc-ice w3c/webrtc-extensions#208, by @dontcallmedom.
-
-
5 issues received 8 new comments.
-
Implementation commitments on RTCEncodingOptions.keyFrame? w3c/webrtc-extensions#213 (4 comments by @dontcallmedom, @fippo)
-
captureTimestamp: RTCRtpContributingSource vs RTCRtpSynchronizationSource w3c/webrtc-extensions#215 (1 comment by @dontcallmedom)
-
ICE improvements: send and prevent ICE check over a candidate pair w3c/webrtc-extensions#209 (1 comment by @dontcallmedom-bot)
-
w3c/webrtc-encoded-transform
-
1 pull request received 3 new comments.
-
Add captureTimestamp and senderCaptureTimeOffset to frame metadata w3c/webrtc-encoded-transform#228 (3 comments by @alvestrand, @jan-ivar)
-
w3c/mediacapture-fromelement
-
2 issues opened.
-
Safari and Chrome exposes different settings for canvas capture tracks w3c/mediacapture-fromelement#101, by @youennf.
-
Different behavior when onaddtrack is fired for element.captureStream w3c/mediacapture-fromelement#100, by @bc-lee.
-
-
2 issues received 3 new comments.
-
Different behavior when onaddtrack is fired for element.captureStream w3c/mediacapture-fromelement#100 (2 comments by @Pehrsons, @steely-glint)
-
w3c/webrtc-charter
-
1 pull request merged.
-
Propose revision to merge guide w3c/webrtc-charter#83.
-
-
1 pull request closed.
-
Add link to WebTransport WG in dependencies w3c/webrtc-charter#66.
-
-
2 pull requests received 2 new comments.
w3c/mediacapture-handle
-
1 issue opened.
-
Some references in the spec have been broken w3c/mediacapture-handle#75, by @eladalon1983.
-
-
2 issues closed.
-
What does capturehandlechange event do when cross documentation navigation happen? w3c/mediacapture-handle#74.
-
Some references in the spec have been broken w3c/mediacapture-handle#75.
-
-
1 issue received 3 new comments.
-
What does capturehandlechange event do when cross documentation navigation happen? w3c/mediacapture-handle#74 (3 comments by @eladalon1983, @xuesichao)
-
-
1 pull request opened.
-
Fix cross-ref to getusermedia w3c/mediacapture-handle#76, by @dontcallmedom.
-
-
1 pull request merged.
-
Fix cross-ref to getusermedia w3c/mediacapture-handle#76.
-
-
1 pull request received 1 new comment.
w3c/mediacapture-transform
-
1 issue closed.
-
Is using ReadableStream/WritableStream the right approach? w3c/mediacapture-transform#4.
-
-
1 issue received 1 new comment.
-
Is using ReadableStream/WritableStream the right approach? w3c/mediacapture-transform#4 (1 comment by @alvestrand)
-
TR publications
-
6 documents published.
-
Media Capture and Streams published twice as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Scalable Video Coding (SVC) Extension for WebRTC published 3 times as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Philip Eliasson (Google LLC) joined.
-
Mark Foltz (Google LLC) joined.
-
-
1 organization joined.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） joined.
-
GitHub
w3c/webrtc-rtptransport
-
10 issues opened.
-
BYOB interfaces to avoid ArrayBuffer churn w3c/webrtc-rtptransport#41, by @tonyherre.
-
Packet forwarding is not supported w3c/webrtc-rtptransport#40, by @Philipel-WebRTC.
-
Potential issues from convenience extensions w3c/webrtc-rtptransport#39, by @aboba.
-
Packet prioritization is not supported. w3c/webrtc-rtptransport#38, by @Philipel-WebRTC.
-
Should RtpSendStream/RtpReceiveStream be transferable? w3c/webrtc-rtptransport#36, by @youennf.
-
RtpSendStreamInit and RtpReceiveStreamInit are not defined in explainer-use-case-1.md w3c/webrtc-rtptransport#35, by @youennf.
-
Only allow RtpTransport (max-bundle) w3c/webrtc-rtptransport#34, by @pthatcher.
-
Make RtpTransportProcessor transferable w3c/webrtc-rtptransport#33, by @pthatcher.
-
How do the two `sendRtp` functions interact? w3c/webrtc-rtptransport#32, by @Philipel-WebRTC.
-
Custom extensions not supported w3c/webrtc-rtptransport#29, by @Philipel-WebRTC.
-
-
9 issues received 33 new comments.
-
Custom extensions not supported w3c/webrtc-rtptransport#29 (8 comments by @aboba, @Philipel-WebRTC, @tonyherre, @youennf)
-
Not requiring per-packet JS Events w3c/webrtc-rtptransport#20 (6 comments by @dontcallmedom-bot, @pthatcher, @tonyherre, @youennf)
-
Should RtpSendStream/RtpReceiveStream be transferable? w3c/webrtc-rtptransport#36 (6 comments by @alvestrand, @tonyherre, @youennf)
-
Make RtpTransportProcessor transferable w3c/webrtc-rtptransport#33 (4 comments by @alvestrand, @dontcallmedom-bot, @pthatcher, @youennf)
-
BYOB interfaces to avoid ArrayBuffer churn w3c/webrtc-rtptransport#41 (2 comments by @aboba, @jesup)
-
Packet prioritization is not supported. w3c/webrtc-rtptransport#38 (2 comments by @Philipel-WebRTC, @tonyherre)
-
Packet forwarding is not supported w3c/webrtc-rtptransport#40 (2 comments by @aboba, @Philipel-WebRTC)
-
How do the two `sendRtp` functions interact? w3c/webrtc-rtptransport#32 (2 comments by @alvestrand, @Philipel-WebRTC)
-
-
4 pull requests opened.
-
Add batch interfaces for reading RtpSents and RtpAcks w3c/webrtc-rtptransport#42, by @tonyherre.
-
Update examples and tweak API w3c/webrtc-rtptransport#37, by @pthatcher.
-
[Bikeshedding] Remove RtpPacketInit convenience extensions. w3c/webrtc-rtptransport#31, by @Philipel-WebRTC.
-
Change RtpHeaderExtension URI to numerical ID. w3c/webrtc-rtptransport#30, by @Philipel-WebRTC.
-
-
2 pull requests merged.
-
Use Case 1: Clarify RTCP, remove custom NACK/RTX w3c/webrtc-rtptransport#28.
-
Update examples and tweak API w3c/webrtc-rtptransport#37.
-
-
4 pull requests received 16 new comments.
-
[Bikeshedding] Remove RtpPacketInit convenience extensions. w3c/webrtc-rtptransport#31 (8 comments by @aboba, @dontcallmedom, @Philipel-WebRTC, @tonyherre)
-
Update examples and tweak API w3c/webrtc-rtptransport#37 (4 comments by @aboba, @pthatcher, @tonyherre)
-
Add batch interfaces for reading RtpSents and RtpAcks w3c/webrtc-rtptransport#42 (3 comments by @aboba, @Philipel-WebRTC, @tonyherre)
-
Use Case 1: Clarify RTCP, remove custom NACK/RTX w3c/webrtc-rtptransport#28 (1 comment by @pthatcher)
-
w3c/webrtc-charter
-
1 issue closed.
-
Update MEIG description w3c/webrtc-charter#78.
-
-
3 pull requests opened.
-
Propose revision to merge guide w3c/webrtc-charter#83, by @dontcallmedom.
-
Update list of deliverables since last charter w3c/webrtc-charter#82, by @dontcallmedom.
-
Align with changes in templates since Apr 2022 w3c/webrtc-charter#81, by @dontcallmedom.
-
-
3 pull requests merged.
-
Update list of deliverables since last charter w3c/webrtc-charter#82.
-
Align with changes in templates since Apr 2022 w3c/webrtc-charter#81.
-
Align coordination with MEIG with reality w3c/webrtc-charter#80.
-
-
2 pull requests received 2 new comments.
w3c/mediacapture-transform
-
1 issue opened.
-
Web Pages and GitHub Pages Outdated since 2022-10-20 w3c/mediacapture-transform#110, by @bc-lee.
-
-
2 issues closed.
-
Web Pages and GitHub Pages Outdated since 2022-10-20 w3c/mediacapture-transform#110.
-
Review mute/unmute/ended and constraints on new VideoTrackGenerator().track w3c/mediacapture-transform#109.
-
-
1 issue received 1 new comment.
-
Web Pages and GitHub Pages Outdated since 2022-10-20 w3c/mediacapture-transform#110 (1 comment by @dontcallmedom)
-
w3c/mediacapture-extensions
-
3 issues opened.
-
Consider adding onVoiceActivity event on MediaStreamTrack for audio w3c/mediacapture-extensions#145, by @taste1981.
-
Add a blackFrames counter to MediaStreamTrackVideoStats w3c/mediacapture-extensions#144, by @guidou.
-
Should we add reasons to MediaStreamTrack.onended w3c/mediacapture-extensions#143, by @youennf.
-
-
1 issue closed.
-
4 issues received 14 new comments.
-
Add a blackFrames counter to MediaStreamTrackVideoStats w3c/mediacapture-extensions#144 (7 comments by @alvestrand, @eladalon1983, @guidou, @youennf)
-
Should we add reasons to MediaStreamTrack.onended w3c/mediacapture-extensions#143 (4 comments by @bradisbell, @eladalon1983, @youennf)
-
Consider adding onVoiceActivity event on MediaStreamTrack for audio w3c/mediacapture-extensions#145 (2 comments by @taste1981, @youennf)
-
MediaStreamTrack resizeMode constraint is too vague to request specific strategy w3c/mediacapture-extensions#7 (1 comment by @anthmFS)
-
-
2 pull requests opened.
-
Allow transfering MediaStreamTrack content hint w3c/mediacapture-extensions#146, by @youennf.
-
Add background segmentation mask w3c/mediacapture-extensions#142, by @eehakkin.
-
-
1 pull request merged.
-
Allow transfering MediaStreamTrack content hint w3c/mediacapture-extensions#146.
-
-
2 pull requests received 16 new comments.
-
Add background segmentation mask w3c/mediacapture-extensions#142 (14 comments by @eehakkin, @eladalon1983, @riju)
-
Allow transfering MediaStreamTrack content hint w3c/mediacapture-extensions#146 (2 comments by @youennf)
-
w3c/webrtc-pc
-
5 issues opened.
-
Write WPT to check RTCIceCandidatePair is now an interface w3c/webrtc-pc#2978, by @jan-ivar.
-
PC.local_description and friends - snapshot views or dynamic views? w3c/webrtc-pc#2977, by @alvestrand.
-
RTCRtpCodecCapability is superfluous and should be deleted from the spec. w3c/webrtc-pc#2974, by @alvestrand.
-
Promises on the operations chain may never settle w3c/webrtc-pc#2973, by @chrisguttandin.
-
Comparison rules for RTCRtpCodec needs clarification on how mimeType is compared w3c/webrtc-pc#2971, by @docfaraday.
-
-
4 issues closed.
-
Consider making RTCIceCandidatePair an interface w3c/webrtc-pc#2930.
-
Comparison rules for RTCRtpCodec needs clarification on how mimeType is compared w3c/webrtc-pc#2971.
-
Review mute/unmute/ended and constraints on RTCRtpReceiver's track. w3c/webrtc-pc#2942.
-
-
7 issues received 20 new comments.
-
Comparison rules for RTCRtpCodec needs clarification on how mimeType is compared w3c/webrtc-pc#2971 (10 comments by @alvestrand, @jan-ivar, @Orphis)
-
Promises on the operations chain may never settle w3c/webrtc-pc#2973 (3 comments by @chrisguttandin, @jan-ivar)
-
Let createOffer and createAnswer resolve with RTCSessionDescription instead of RTCSessionDescriptionInit w3c/webrtc-pc#922 (3 comments by @fippo, @jan-ivar)
-
PC.local_description and friends - snapshot views or dynamic views? w3c/webrtc-pc#2977 (1 comment by @youennf)
-
WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track receiving mute/unmute w3c/webrtc-pc#2915 (1 comment by @jan-ivar)
-
Review mute/unmute/ended and constraints on RTCRtpReceiver's track. w3c/webrtc-pc#2942 (1 comment by @jan-ivar)
-
Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel w3c/webrtc-pc#2931 (1 comment by @gunnarhm)
-
-
6 pull requests opened.
-
Collapse RTCRtpCodecCapability. w3c/webrtc-pc#2976, by @jan-ivar.
-
setCodecPreferences() must use case-insensitive mimeType comparison w3c/webrtc-pc#2975, by @jan-ivar.
-
Separate Send/ReceiveCodecs and NegotiatedCodecs w3c/webrtc-pc#2972, by @alvestrand.
-
Update to ReSpec version 35.0.2 w3c/webrtc-pc#2970, by @dontcallmedom.
-
Clarify description.toJSON() returns RTCSessionDescriptionInit w3c/webrtc-pc#2969, by @jan-ivar.
-
Clarify description.toJSON() returns RTCSessionDescriptionInit w3c/webrtc-pc#2968, by @jan-ivar.
-
-
5 pull requests merged.
-
Convert RTCIceCandidatePair dictionary to an interface w3c/webrtc-pc#2961.
-
setCodecPreferences() must use case-insensitive mimeType comparison w3c/webrtc-pc#2975.
-
Clarify description.toJSON() returns RTCSessionDescriptionInit w3c/webrtc-pc#2969.
-
Complete amendments description w3c/webrtc-pc#2963.
-
Update to ReSpec version 35.0.2 w3c/webrtc-pc#2970.
-
-
1 pull request closed.
-
Clarify description.toJSON() returns RTCSessionDescriptionInit w3c/webrtc-pc#2968.
-
-
4 pull requests received 12 new comments.
-
Separate Send/ReceiveCodecs and NegotiatedCodecs w3c/webrtc-pc#2972 (6 comments by @alvestrand, @jan-ivar)
-
Convert RTCIceCandidatePair dictionary to an interface w3c/webrtc-pc#2961 (4 comments by @alvestrand, @dontcallmedom, @sam-vi)
-
setCodecPreferences() must use case-insensitive mimeType comparison w3c/webrtc-pc#2975 (1 comment by @jan-ivar)
-
Clarify description.toJSON() returns RTCSessionDescriptionInit w3c/webrtc-pc#2968 (1 comment by @jan-ivar)
-
w3c/mediacapture-main
-
3 issues opened.
-
How to handle specs that extend MediaStreamTrack, in particular MediaStreamTrack slots? w3c/mediacapture-main#1004, by @youennf.
-
repo name nit: it'd be nice if this were simply w3c/mediacapture w3c/mediacapture-main#1003, by @hober.
-
-
2 issues closed.
-
Confusingly redundant prose in § 4.3.1 Life-cycle and Media Flow w3c/mediacapture-main#994.
-
-
7 issues received 20 new comments.
-
risk model of stored permissions and constraint opportunities w3c/mediacapture-main#991 (7 comments by @jan-ivar, @rockinghelvetica)
-
repo name nit: it'd be nice if this were simply w3c/mediacapture w3c/mediacapture-main#1003 (6 comments by @alvestrand, @dontcallmedom, @dontcallmedom-bot, @eladalon1983, @jan-ivar)
-
I got an issue for capture audio from other applications while using GetDisplayMedia for screen sharing in a React Native app. w3c/mediacapture-main#1002 (3 comments by @alvestrand, @eladalon1983, @priyankgandhi0)
-
How to handle specs that extend MediaStreamTrack, in particular MediaStreamTrack slots? w3c/mediacapture-main#1004 (1 comment by @youennf)
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Update to latest ReSpec version 35.0.2 w3c/mediacapture-main#1001, by @dontcallmedom.
-
-
4 pull requests merged.
-
Remove redundant statements about muted/enabled. w3c/mediacapture-main#998.
-
Update to latest ReSpec version 35.0.2 w3c/mediacapture-main#1001.
-
Fix DeviceChangeEventInit WebIDL definition w3c/mediacapture-main#1000.
-
Editorial: Align with Web IDL specification w3c/mediacapture-main#999.
-
-
2 pull requests received 5 new comments.
-
Remove redundant statements about muted/enabled. w3c/mediacapture-main#998 (3 comments by @alvestrand, @guidou, @jan-ivar)
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Current steps are inefficient and difficult to build on. Cleanup needed w3c/webrtc-encoded-transform#229, by @jan-ivar.
-
-
2 issues received 8 new comments.
-
Expose RTCEncodedAudioFrame interface in AudioWorklets w3c/webrtc-encoded-transform#226 (7 comments by @dontcallmedom-bot, @Orphis, @padenot, @youennf)
-
Should we add captureTimestamp senderCaptureTimeOffset to the RTCEncodedXXXFrameMetadata if abs-capture-time is used? w3c/webrtc-encoded-transform#225 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Add captureTimestamp and senderCaptureTimeOffset to frame metadata w3c/webrtc-encoded-transform#228, by @Orphis.
-
-
2 pull requests received 12 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (7 comments by @jan-ivar)
-
Add captureTimestamp and senderCaptureTimeOffset to frame metadata w3c/webrtc-encoded-transform#228 (5 comments by @aboba, @alvestrand, @dontcallmedom-bot, @jan-ivar, @Orphis)
-
w3c/mst-content-hint
-
2 issues opened.
-
Spec should be integrated into other specs w3c/mst-content-hint#59, by @alvestrand.
-
The "application-defined content hint" definition should be exported w3c/mst-content-hint#58, by @alvestrand.
-
w3c/mediacapture-handle
-
1 issue opened.
-
What does capturehandlechange event do when cross documentation navigation happen? w3c/mediacapture-handle#74, by @xuesichao.
-
-
1 issue received 1 new comment.
-
What does capturehandlechange event do when cross documentation navigation happen? w3c/mediacapture-handle#74 (1 comment by @eladalon1983)
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 3 new comments.
-
Capturing audio-only w3c/mediacapture-screen-share-extensions#12 (3 comments by @eladalon1983, @ryabenko-pro, @salvymc)
-
w3c/webrtc-extensions
-
1 issue opened.
-
Post-Quantum Crypto (PQC) support in WebRTC w3c/webrtc-extensions#207, by @aboba.
-
-
2 issues received 2 new comments.
-
Add jitterBufferMaximumDelay attribute to RTCRtpReceiver w3c/webrtc-extensions#199 (1 comment by @eldarrello)
-
1 pull request closed.
-
Add RTCRtpEncodedSource and explainer w3c/webrtc-extensions#198.
-
-
1 pull request received 3 new comments.
-
Clarify when `icecandidatepairremove` is fired. w3c/webrtc-extensions#204 (3 comments by @alvestrand, @sam-vi)
-
w3c/mediacapture-screen-share
-
1 issue opened.
-
Multiple Windows are shared and the previous window is overwritten by the latest window w3c/mediacapture-screen-share#302, by @trookie2000.
-
-
1 issue closed.
-
Review mute/unmute/ended and constraints on tracks from getDisplayMedia() w3c/mediacapture-screen-share#298.
-
-
3 issues received 3 new comments.
-
Detect when minimizing a window pauses capture (was: Capability polling - capture-while-minimized) w3c/mediacapture-screen-share#257 (1 comment by @eladalon1983)
-
Review mute/unmute/ended and constraints on tracks from getDisplayMedia() w3c/mediacapture-screen-share#298 (1 comment by @jan-ivar)
-
Multiple Windows are shared and the previous window is overwritten by the latest window w3c/mediacapture-screen-share#302 (1 comment by @trookie2000)
-
-
1 pull request received 1 new comment.
w3c/webrtc-stats
-
1 pull request received 1 new comment.
-
raddr+rport can be set for peer-reflexive candidates as well w3c/webrtc-stats#783 (1 comment by @fippo)
-
w3c/mediacapture-fromelement
-
1 issue closed.
-
Review mute/unmute/ended and constraints on tracks from canvas.captureStream() w3c/mediacapture-fromelement#99.
-
w3c/webrtc-svc
-
1 issue opened.
-
Discovery: Where does this material belong? w3c/webrtc-svc#103, by @aboba.
-
-
1 issue closed.
-
Discovery: Where does this material belong? w3c/webrtc-svc#103.
-
-
1 pull request opened.
-
Remove Discovery Section w3c/webrtc-svc#104, by @aboba.
-
-
1 pull request merged.
-
Remove Discovery Section w3c/webrtc-svc#104.
-
-
1 pull request received 1 new comment.
w3c/webrtc-nv-use-cases
-
1 issue received 1 new comment.
-
Section 3.10.1: Live encoded non-WebRTC media use case not compelling w3c/webrtc-nv-use-cases#100 (1 comment by @ltsg123)
-
-
1 pull request received 5 new comments.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (5 comments by @aboba, @stefhak, @xingri)
-
TR publications
-
2 documents published.
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
WebRTC Encoded Transform published as a Working Draft. History of WebRTC Encoded Transform
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Lei Zhao (China Mobile Communications Corporation) joined.
-
Erik Språng (Google LLC) joined.
-
-
1 participant left.
-
Mike English (Mux) left.
-
-
1 organization left.
-
Mux left.
-
GitHub
w3c/mediacapture-main
-
1 issue opened.
-
Confusingly redundant prose in § 4.3.1 Life-cycle and Media Flow w3c/mediacapture-main#994, by @jan-ivar.
-
-
2 issues closed.
-
The [=muted=] concept is exported wrongly w3c/mediacapture-main#985.
-
Racy devicechange event design has poor interoperability w3c/mediacapture-main#972.
-
-
4 issues received 7 new comments.
-
risk model of stored permissions and constraint opportunities w3c/mediacapture-main#991 (2 comments by @jan-ivar)
-
Racy devicechange event design has poor interoperability w3c/mediacapture-main#972 (2 comments by @dontcallmedom-bot, @jan-ivar)
-
(webkit|moz)getUserMedia usage and webcompat issues w3c/mediacapture-main#992 (2 comments by @foolip, @jan-ivar)
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966 (1 comment by @jan-ivar)
-
-
6 pull requests opened.
-
Fix DeviceChangeEventInit WebIDL definition w3c/mediacapture-main#1000, by @chrisguttandin.
-
Editorial: Align with Web IDL specification w3c/mediacapture-main#999, by @autokagami.
-
Remove redundant statements about muted/enabled. w3c/mediacapture-main#998, by @jan-ivar.
-
Update to latest ReSpec version 35.0.0 w3c/mediacapture-main#997, by @dontcallmedom.
-
Add DeviceChangeEvent interface. w3c/mediacapture-main#996, by @jan-ivar.
-
Reorder Media Flow and Life-cycle sections. w3c/mediacapture-main#995, by @jan-ivar.
-
-
4 pull requests merged.
-
Reorder Media Flow and Life-cycle sections. w3c/mediacapture-main#995.
-
Fix export of track-muted and set-track-muted. w3c/mediacapture-main#986.
-
Add DeviceChangeEvent interface. w3c/mediacapture-main#996.
-
Update to latest ReSpec version 35.0.0 w3c/mediacapture-main#997.
-
-
4 pull requests received 18 new comments.
-
Fix export of track-muted and set-track-muted. w3c/mediacapture-main#986 (14 comments by @dontcallmedom, @jan-ivar, @marcoscaceres)
-
w3c/webrtc-rtptransport
-
3 issues opened.
-
Clarify RTCP use of Use Case 1 w3c/webrtc-rtptransport#27, by @pthatcher.
-
Use case 1: NACK/RTX control and RTCP w3c/webrtc-rtptransport#26, by @aboba.
-
Not requiring per-packet JS Events w3c/webrtc-rtptransport#20, by @tonyherre.
-
-
1 issue closed.
-
Use case 1: NACK/RTX control and RTCP w3c/webrtc-rtptransport#26.
-
-
2 issues received 2 new comments.
-
6 pull requests opened.
-
Use Case 1: Clarify RTCP, remove custom NACK/RTX w3c/webrtc-rtptransport#28, by @aboba.
-
Add example using batched reads w3c/webrtc-rtptransport#25, by @tonyherre.
-
Be explicit in UC2 that the app gets feedback on UA-packetized packets w3c/webrtc-rtptransport#24, by @tonyherre.
-
Allow custom pacer/BWE to be more piecemeal w3c/webrtc-rtptransport#23, by @pthatcher.
-
Remove UC1's custom seq num & document this in handled by the UA w3c/webrtc-rtptransport#22, by @tonyherre.
-
Remove references to encoded frame transform API from Use Case 1 w3c/webrtc-rtptransport#21, by @tonyherre.
-
-
5 pull requests merged.
-
Be explicit in UC2 that the app gets feedback on UA-packetized packets w3c/webrtc-rtptransport#24.
-
Allow custom pacer/BWE to be more piecemeal w3c/webrtc-rtptransport#23.
-
Remove UC1's custom seq num & document this in handled by the UA w3c/webrtc-rtptransport#22.
-
Remove references to encoded frame transform API from Use Case 1 w3c/webrtc-rtptransport#21.
-
Add example using batched reads w3c/webrtc-rtptransport#25.
-
-
2 pull requests received 12 new comments.
-
Allow custom pacer/BWE to be more piecemeal w3c/webrtc-rtptransport#23 (11 comments by @pthatcher, @tonyherre)
-
Remove UC1's custom seq num & document this in handled by the UA w3c/webrtc-rtptransport#22 (1 comment by @aboba)
-
w3c/webrtc-pc
-
5 issues opened.
-
Implementations only update getParameters().codecs when negotiation has finished w3c/webrtc-pc#2967, by @jan-ivar.
-
setCodecPreferences should trigger negotiationneeded w3c/webrtc-pc#2964, by @jan-ivar.
-
setCodecPreferences should take sequence<RTCRtpCodec> w3c/webrtc-pc#2959, by @jan-ivar.
-
receiver.getParameters().codecs is broken (regression) w3c/webrtc-pc#2956, by @jan-ivar.
-
Confusion over duplicates in setCodecPreferences? Why allow them? w3c/webrtc-pc#2955, by @jan-ivar.
-
-
4 issues closed.
-
setCodecPreferences should take sequence<RTCRtpCodec> w3c/webrtc-pc#2959.
-
Confusion over duplicates in setCodecPreferences? Why allow them? w3c/webrtc-pc#2955.
-
RTCSessionDescriptionInit vs "local" RTCLocalSessionDescriptionInit w3c/webrtc-pc#2940.
-
Incorporate jitterBufferTarget w3c/webrtc-pc#2952.
-
-
10 issues received 37 new comments.
-
Confusion over duplicates in setCodecPreferences? Why allow them? w3c/webrtc-pc#2955 (10 comments by @aboba, @jan-ivar)
-
setCodecPreferences, sendonly codecs and dummy codecs w3c/webrtc-pc#2937 (9 comments by @aboba, @rshpount, @stefhak)
-
receiver.getParameters().codecs is broken (regression) w3c/webrtc-pc#2956 (4 comments by @alvestrand, @jan-ivar)
-
Implementations only update getParameters().codecs when negotiation has finished w3c/webrtc-pc#2967 (3 comments by @alvestrand, @jan-ivar)
-
setCodecPreferences should trigger negotiationneeded w3c/webrtc-pc#2964 (3 comments by @alvestrand, @jan-ivar)
-
Alternative storage for RTCCertificates needed w3c/webrtc-pc#2944 (3 comments by @steely-glint, @youennf)
-
Add support for WebRTC Data Channel in Workers w3c/webrtc-pc#230 (2 comments by @aboba, @epaterlini)
-
Proposing setCodecPreferences to deal with both send and recv codecs w3c/webrtc-pc#2939 (1 comment by @aboba)
-
RTCSessionDescriptionInit vs "local" RTCLocalSessionDescriptionInit w3c/webrtc-pc#2940 (1 comment by @jan-ivar)
-
-
9 pull requests opened.
-
Replace references to RFC8829 with RFC9429 w3c/webrtc-pc#2966, by @dontcallmedom.
-
Update to ReSpec version 35.0.0 w3c/webrtc-pc#2965, by @dontcallmedom.
-
Complete amendments description w3c/webrtc-pc#2963, by @dontcallmedom.
-
Avoid setCodecPreferences confusion over which duplicates are removed w3c/webrtc-pc#2962, by @jan-ivar.
-
Convert RTCIceCandidatePair dictionary to an interface w3c/webrtc-pc#2961, by @sam-vi.
-
Have setCodecPreferences take sequence<RTCRtpCodec> w3c/webrtc-pc#2960, by @jan-ivar.
-
Rename to "codec dictionary match" algorithm and remove index consistency claim w3c/webrtc-pc#2958, by @jan-ivar.
-
Export RTCRtpReceiver.ReceiveCodec w3c/webrtc-pc#2957, by @alvestrand.
-
Fix amendments w3c/webrtc-pc#2954, by @dontcallmedom.
-
-
8 pull requests merged.
-
Replace references to RFC8829 with RFC9429 w3c/webrtc-pc#2966.
-
Avoid setCodecPreferences confusion over which duplicates are removed w3c/webrtc-pc#2962.
-
Update to ReSpec version 35.0.0 w3c/webrtc-pc#2965.
-
Have setCodecPreferences take sequence<RTCRtpCodec> w3c/webrtc-pc#2960.
-
Rename to "codec dictionary match" algorithm and remove index consistency claim w3c/webrtc-pc#2958.
-
Export RTCRtpReceiver.ReceiveCodec w3c/webrtc-pc#2957.
-
Integrate jitterBufferTarget as candidate addition w3c/webrtc-pc#2953.
-
Fix amendments w3c/webrtc-pc#2954.
-
-
2 pull requests received 4 new comments.
-
Convert RTCIceCandidatePair dictionary to an interface w3c/webrtc-pc#2961 (2 comments by @alvestrand, @dontcallmedom)
-
Rename to "codec dictionary match" algorithm and remove index consistency claim w3c/webrtc-pc#2958 (2 comments by @alvestrand, @jan-ivar)
-
w3c/webrtc-ice
-
1 issue opened.
-
Rename `onerror` to `onicecandidateerror`? w3c/webrtc-ice#47, by @tidoust.
-
w3c/webrtc-extensions
-
2 issues received 2 new comments.
-
Add steps to clear [[CandidatePairs]] in response to ICE restart w3c/webrtc-extensions#196 (1 comment by @sam-vi)
-
Add jitterBufferMaximumDelay attribute to RTCRtpReceiver w3c/webrtc-extensions#199 (1 comment by @alvestrand)
-
-
3 pull requests opened.
-
Fix links by s/codec match/codec dictionary match/ w3c/webrtc-extensions#206, by @jan-ivar.
-
Use RTCIceCandidatePair interface in RTCIceTransport w3c/webrtc-extensions#205, by @sam-vi.
-
Clarify when `icecandidatepairremove` is fired. w3c/webrtc-extensions#204, by @sam-vi.
-
-
3 pull requests merged.
-
Fix links by s/codec match/codec dictionary match/ w3c/webrtc-extensions#206.
-
Clean references and fix links w3c/webrtc-extensions#202.
-
Move jitterBufferTarget to main spec w3c/webrtc-extensions#203.
-
-
1 pull request received 1 new comment.
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Accessing the data from RTP header extensions w3c/webrtc-encoded-transform#227, by @destructeur.
-
-
1 issue received 2 new comments.
-
Accessing the data from RTP header extensions w3c/webrtc-encoded-transform#227 (2 comments by @destructeur, @fippo)
-
-
1 pull request merged.
-
Constructor frame w3c/webrtc-encoded-transform#223.
-
-
3 pull requests received 17 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (4 comments by @alvestrand, @dontcallmedom-bot)
-
IDL changes for setMetadata for 3.2.2 webrtc nv use case w3c/webrtc-encoded-transform#202 (2 comments by @alvestrand, @dontcallmedom-bot)
w3c/mediacapture-extensions
-
1 issue received 1 new comment.
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (1 comment by @fbueckle)
-
-
1 pull request merged.
-
Expose MediaStream in workers w3c/mediacapture-extensions#26.
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 8 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (8 comments by @dontcallmedom-bot, @jan-ivar, @tovepet, @youennf)
-
w3c/webrtc-stats
-
1 issue received 1 new comment.
w3c/webrtc-nv-use-cases
-
2 pull requests received 7 new comments.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (6 comments by @alvestrand, @stefhak, @xingri)
-
Section 3.2.1: Add N49 - video decoding recovery after packet loss w3c/webrtc-nv-use-cases#129 (1 comment by @stefhak)
-
w3c/mediacapture-record
-
1 issue received 1 new comment.
-
Provide a way to specify custom encoder (to generate other types of formats) w3c/mediacapture-record#60 (1 comment by @pirate)
-
w3c/webrtc-priority
-
1 issue opened.
-
Update references w3c/webrtc-priority#23, by @stefhak.
-
w3c/mediacapture-image
-
1 issue received 1 new comment.
-
Provide way to get / set captured image format w3c/mediacapture-image#162 (1 comment by @SaharHusseini)
-
TR publications
-
1 document published.
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Past meetings
-
1 meeting.
Participants
-
2 participants left.
-
Qiang Chen (Google LLC) left.
-
Philipp Hancke (Microsoft Corporation) left.
-
GitHub
w3c/webrtc-nv-use-cases
-
1 issue opened.
-
Add picture timing requirement to Ultra Low latency Broadcast with Fanout use case w3c/webrtc-nv-use-cases#130, by @murillo128.
-
-
2 pull requests received 10 new comments.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (5 comments by @aboba, @dontcallmedom-bot, @xingri)
-
Section 3.2.1: Add N49 - video decoding recovery after packet loss w3c/webrtc-nv-use-cases#129 (5 comments by @aboba, @dontcallmedom-bot, @stefhak, @xingri)
-
w3c/mediacapture-image
-
1 pull request received 1 new comment.
-
Use constrainable pattern for ImageCapture (second take) w3c/mediacapture-image#150 (1 comment by @Amjidkhan6061)
-
w3c/mediacapture-output
-
1 issue opened.
-
Set Preferred (default) Audio Output Device in MediaDevices w3c/mediacapture-output#141, by @sunggook.
-
-
1 issue closed.
-
Persisting deviceIds Across Sessions w3c/mediacapture-output#127.
-
-
1 issue received 1 new comment.
w3c/webrtc-pc
-
3 issues opened.
-
Incorporate jitterBufferTarget w3c/webrtc-pc#2952, by @dontcallmedom.
-
Missing tests for candidate amendments w3c/webrtc-pc#2950, by @dontcallmedom.
-
RTCIceCandidate's relayProtocol and url members can be null but not absent w3c/webrtc-pc#2947, by @jan-ivar.
-
-
4 issues closed.
-
Put a=end-of-candidates into description(s) w3c/webrtc-pc#2896.
-
Redundant queuing in gathering state computation risks eliding events w3c/webrtc-pc#2892.
-
ICE finished gathering algorithm touches state after firing an event w3c/webrtc-pc#2893.
-
RTCIceCandidate's relayProtocol and url members can be null but not absent w3c/webrtc-pc#2947.
-
-
7 issues received 17 new comments.
-
Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel w3c/webrtc-pc#2931 (5 comments by @aboba, @cdh4u, @dontcallmedom, @gunnarhm)
-
Consider making RTCIceCandidatePair an interface w3c/webrtc-pc#2930 (4 comments by @foolip, @jan-ivar)
-
Alternative storage for RTCCertificates needed w3c/webrtc-pc#2944 (3 comments by @dontcallmedom-bot, @steely-glint)
-
Proposing setCodecPreferences to deal with both send and recv codecs w3c/webrtc-pc#2939 (2 comments by @aboba, @jan-ivar)
-
WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track receiving mute/unmute w3c/webrtc-pc#2915 (1 comment by @dontcallmedom-bot)
-
Review mute/unmute/ended and constraints on RTCRtpReceiver's track. w3c/webrtc-pc#2942 (1 comment by @dontcallmedom-bot)
-
Clarify unmute event must fire on receiver.track AFTER sRD(offer) succeeds w3c/webrtc-pc#2880 (1 comment by @jan-ivar)
-
-
5 pull requests opened.
-
Integrate jitterBufferTarget as candidate addition w3c/webrtc-pc#2953, by @dontcallmedom.
-
Make RTCIceCandidatePair members required w3c/webrtc-pc#2951, by @foolip.
-
Fix bugs in amendments w3c/webrtc-pc#2949, by @dontcallmedom.
-
Clarify when RTCIceCandidate's relayProtocol and url members are null. w3c/webrtc-pc#2948, by @jan-ivar.
-
Update to ReSpec version 34.5.0 w3c/webrtc-pc#2946, by @dontcallmedom.
-
-
6 pull requests merged.
-
Make RTCIceCandidatePair members required w3c/webrtc-pc#2951.
-
Fix bugs in amendments w3c/webrtc-pc#2949.
-
Clarify when RTCIceCandidate's relayProtocol and url members are null. w3c/webrtc-pc#2948.
-
Document test updates associated with amendments w3c/webrtc-pc#2910.
-
Update to ReSpec version 34.5.0 w3c/webrtc-pc#2946.
-
3 pull requests received 13 new comments.
-
Document test updates associated with amendments w3c/webrtc-pc#2910 (9 comments by @dontcallmedom, @jan-ivar, @youennf)
-
Queue two tasks upon finishing ICE gathering, and fire gatheringstatechange & icegatheringstatechange in same task w3c/webrtc-pc#2894 (3 comments by @dontcallmedom, @jan-ivar)
-
Clarify when RTCIceCandidate's relayProtocol and url members are null. w3c/webrtc-pc#2948 (1 comment by @alvestrand)
-
w3c/webrtc-extensions
-
1 issue opened.
-
Clarify status of RTP Header Extension for Absolute Capture Time w3c/webrtc-extensions#201, by @dontcallmedom.
-
-
2 issues received 16 new comments.
-
Add jitterBufferMaximumDelay attribute to RTCRtpReceiver w3c/webrtc-extensions#199 (15 comments by @alvestrand, @eldarrello, @jakobivarsson)
-
-
2 pull requests opened.
-
Move jitterBufferTarget to main spec w3c/webrtc-extensions#203, by @dontcallmedom.
-
Clean references and fix links w3c/webrtc-extensions#202, by @dontcallmedom.
-
-
1 pull request received 17 new comments.
-
Add RTCRtpEncodedSource and explainer w3c/webrtc-extensions#198 (17 comments by @aboba, @dontcallmedom-bot, @guidou, @jan-ivar, @youennf)
-
w3c/webrtc-rtptransport
-
3 pull requests opened.
-
Add "motivation" section, largely copied from IceController explainer w3c/webrtc-rtptransport#19, by @pthatcher.
-
Add "Use Case 2" w3c/webrtc-rtptransport#18, by @pthatcher.
-
Cleanup Use Case 1 w3c/webrtc-rtptransport#17, by @pthatcher.
-
-
3 pull requests merged.
-
Add "motivation" section, largely copied from IceController explainer w3c/webrtc-rtptransport#19.
-
Add "Use Case 2" w3c/webrtc-rtptransport#18.
-
Cleanup Use Case 1 w3c/webrtc-rtptransport#17.
-
-
1 pull request received 1 new comment.
-
Add "motivation" section, largely copied from IceController explainer w3c/webrtc-rtptransport#19 (1 comment by @tonyherre)
-
w3c/mediacapture-extensions
-
1 issue closed.
-
Should web applications be aware of reaction effects added by OS to camera feeds? w3c/mediacapture-extensions#118.
-
-
2 issues received 6 new comments.
-
Should web applications be aware of reaction effects added by OS to camera feeds? w3c/mediacapture-extensions#118 (5 comments by @alexandermaisey, @dontcallmedom-bot, @eladalon1983, @fippo, @jnoring-hv)
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (1 comment by @ivancuric)
-
-
1 pull request opened.
-
Add support for gesture reactions constraint w3c/mediacapture-extensions#141, by @jan-ivar.
-
-
1 pull request merged.
-
Add support for gesture reactions constraint w3c/mediacapture-extensions#141.
-
-
1 pull request received 10 new comments.
-
Add support for gesture reactions constraint w3c/mediacapture-extensions#141 (10 comments by @dontcallmedom-bot, @eladalon1983, @jan-ivar, @youennf)
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Expose RTCEncodedAudioFrame interface in AudioWorklets w3c/webrtc-encoded-transform#226, by @tonyherre.
-
-
5 issues received 15 new comments.
-
Expose RTCEncodedAudioFrame interface in AudioWorklets w3c/webrtc-encoded-transform#226 (6 comments by @jan-ivar, @padenot, @tonyherre, @youennf)
-
Generalize ScriptTransform constructor to allow main-thread processing w3c/webrtc-encoded-transform#89 (4 comments by @jan-ivar, @lgrahl)
-
Should we add captureTimestamp senderCaptureTimeOffset to the RTCEncodedXXXFrameMetadata if abs-capture-time is used? w3c/webrtc-encoded-transform#225 (2 comments by @guidou, @stefanholmer)
-
Expose captureTimestamp to RTCEncodedAudioFrame and RTCEncodedVideoFrame w3c/webrtc-encoded-transform#159 (1 comment by @guidou)
-
-
1 pull request received 4 new comments.
-
Constructor frame w3c/webrtc-encoded-transform#223 (4 comments by @dontcallmedom-bot, @jan-ivar, @youennf)
-
w3c/mediacapture-screen-share-extensions
-
3 issues received 7 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (4 comments by @eladalon1983, @jan-ivar)
-
Capturing audio-only w3c/mediacapture-screen-share-extensions#12 (2 comments by @Pavinati, @salvymc)
-
Multi-capture (concurrent capture of multiple surfaces) w3c/mediacapture-screen-share-extensions#8 (1 comment by @trookie2000)
-
w3c/mediacapture-fromelement
-
3 issues closed.
-
WG CR review for mediacapture-fromelement w3c/mediacapture-fromelement#50.
-
CD publication of specification w3c/mediacapture-fromelement#47.
-
What happens to the audio being rendered to a Media Element when it gets captureStream()ed w3c/mediacapture-fromelement#34.
-
-
8 issues received 8 new comments.
-
Inconsistency: Taint, not mute cross-origin element tracks w3c/mediacapture-fromelement#83 (1 comment by @dontcallmedom-bot)
-
define behaviors of the common ConstrainablePattern Interfaces w3c/mediacapture-fromelement#48 (1 comment by @dontcallmedom-bot)
-
Review mute/unmute/ended and constraints on tracks from element.captureStream() w3c/mediacapture-fromelement#98 (1 comment by @dontcallmedom-bot)
-
Review mute/unmute/ended and constraints on tracks from canvas.captureStream() w3c/mediacapture-fromelement#99 (1 comment by @dontcallmedom-bot)
-
Clarify if CanvasCaptureMediaStreamTrack mute, unmute, and ended events are expected to be fired w3c/mediacapture-fromelement#82 (1 comment by @dontcallmedom-bot)
-
What happens to the audio being rendered to a Media Element when it gets captureStream()ed w3c/mediacapture-fromelement#34 (1 comment by @jan-ivar)
-
w3c/mediacapture-main
-
2 issues opened.
-
(webkit|moz)getUserMedia usage and webcompat issues w3c/mediacapture-main#992, by @karlcow.
-
risk model of stored permissions and constraint opportunities w3c/mediacapture-main#991, by @rockinghelvetica.
-
-
4 issues received 15 new comments.
-
(webkit|moz)getUserMedia usage and webcompat issues w3c/mediacapture-main#992 (11 comments by @beaufortfrancois, @eladalon1983, @fippo, @gsnedders, @karlcow)
-
risk model of stored permissions and constraint opportunities w3c/mediacapture-main#991 (2 comments by @eladalon1983, @rockinghelvetica)
-
Clarify each source is responsible for specifying mute/unmute/ended and constraints behavior w3c/mediacapture-main#984 (1 comment by @dontcallmedom-bot)
-
Implementers must not refuse to open sources set as default at the machine: "DOMException: Could not start audio source" is not in the specification w3c/mediacapture-main#708 (1 comment by @guidou)
-
-
2 pull requests opened.
-
Update to latest ReSpec version 34.5.0 w3c/mediacapture-main#993, by @dontcallmedom.
-
Add class="informative" to "Legacy GetUserMedia interface" section w3c/mediacapture-main#990, by @gsnedders.
-
-
2 pull requests merged.
-
Update to latest ReSpec version 34.5.0 w3c/mediacapture-main#993.
-
Add class="informative" to "Legacy GetUserMedia interface" section w3c/mediacapture-main#990.
-
-
1 pull request received 2 new comments.
-
Fix export of track-muted and set-track-muted. w3c/mediacapture-main#986 (2 comments by @dontcallmedom, @jan-ivar)
-
w3c/mediacapture-record
-
1 issue received 1 new comment.
-
mimeType ambiguity: "video/webm;codecs=vp8" means? w3c/mediacapture-record#194 (1 comment by @dontcallmedom-bot)
-
w3c/mediacapture-transform
-
2 issues received 2 new comments.
-
Review mute/unmute/ended and constraints on new VideoTrackGenerator().track w3c/mediacapture-transform#109 (1 comment by @dontcallmedom-bot)
-
Is MediaStreamTrackProcessor for audio necessary? w3c/mediacapture-transform#29 (1 comment by @mehagar)
-
w3c/mediacapture-screen-share
-
1 issue received 1 new comment.
-
Review mute/unmute/ended and constraints on tracks from getDisplayMedia() w3c/mediacapture-screen-share#298 (1 comment by @dontcallmedom-bot)
-
-
1 pull request received 1 new comment.
w3c/mediacapture-region
-
2 issues opened.
-
is this still an experimental feature? w3c/mediacapture-region#82, by @spxneo.
-
Behavior when full screened w3c/mediacapture-region#81, by @TomiS.
-
-
2 issues closed.
-
is this still an experimental feature? w3c/mediacapture-region#82.
-
Behavior when full screened w3c/mediacapture-region#81.
-
-
2 issues received 4 new comments.
-
is this still an experimental feature? w3c/mediacapture-region#82 (2 comments by @eladalon1983, @spxneo)
-
w3c/webrtc-stats
-
2 issues opened.
-
RTCStats.timestamp - fingerprinting and since epoch w3c/webrtc-stats#786, by @hamishwillee.
-
RTCCodecStats.clockRate - media sampling rate or the codec clock rate? w3c/webrtc-stats#785, by @hamishwillee.
-
-
1 pull request merged.
-
sync local-candidate url definition with webrtc-pc w3c/webrtc-stats#782.
-
-
1 pull request received 2 new comments.
w3c/webrtc-svc
-
1 issue opened.
-
Dependency on AV1 RTP payload specification w3c/webrtc-svc#102, by @aboba.
-
TR publications
-
4 documents published.
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Scalable Video Coding (SVC) Extension for WebRTC published twice as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Screen Capture published as a Working Draft. History of Screen Capture
-
Past meetings
-
1 meeting.
GitHub
w3c/mediacapture-main
-
2 issues closed.
-
Clarify each source is responsible for specifying mute/unmute/ended and constraints behavior w3c/mediacapture-main#984.
-
Web compat issue with permissions.query() in non-persistent permission models w3c/mediacapture-main#928.
-
-
7 issues received 12 new comments.
-
Should getCapabilities() return an empty array or undefined for facingMode? w3c/mediacapture-main#969 (4 comments by @alvestrand, @guidou, @jan-ivar)
-
getUserMedia "hanging" indefinitely w3c/mediacapture-main#846 (2 comments by @alvestrand, @jan-ivar)
-
Width/height as setting should be configured, not native. w3c/mediacapture-main#909 (2 comments by @jan-ivar)
-
Implementers must not refuse to open sources set as default at the machine: "DOMException: Could not start audio source" is not in the specification w3c/mediacapture-main#708 (1 comment by @Bug-Reaper)
-
How should MediaStreamTrack interact with BFCache? w3c/mediacapture-main#974 (1 comment by @dontcallmedom-bot)
-
Web compat issue with permissions.query() in non-persistent permission models w3c/mediacapture-main#928 (1 comment by @jan-ivar)
-
-
1 pull request opened.
-
Update to latest ReSpec version 34.4.0 w3c/mediacapture-main#989, by @dontcallmedom.
-
-
2 pull requests merged.
-
Add guidance for defining a new source of MediaStreamTrack w3c/mediacapture-main#988.
-
Update to latest ReSpec version 34.4.0 w3c/mediacapture-main#989.
-
-
1 pull request closed.
-
Mark sampleRate, sampleSize, and latency are at risk w3c/mediacapture-main#987.
-
-
3 pull requests received 27 new comments.
-
Add guidance for defining a new source of MediaStreamTrack w3c/mediacapture-main#988 (13 comments by @alvestrand, @dontcallmedom-bot, @jan-ivar, @youennf)
-
Fix export of track-muted and set-track-muted. w3c/mediacapture-main#986 (13 comments by @alvestrand, @dontcallmedom, @jan-ivar, @youennf)
-
Mark sampleRate, sampleSize, and latency are at risk w3c/mediacapture-main#987 (1 comment by @jan-ivar)
-
w3c/mediacapture-screen-share
-
3 issues opened.
-
Want to restrict the options of the getDisplayMedia API w3c/mediacapture-screen-share#300, by @Nitesh2503.
-
getUserMedia media streams capturing issue in MV3 (chrome extension) with respect to constraints w3c/mediacapture-screen-share#299, by @Nitesh2503.
-
Review mute/unmute/ended and constraints on tracks from getDisplayMedia() w3c/mediacapture-screen-share#298, by @jan-ivar.
-
-
6 issues closed.
-
Want to restrict the options of the getDisplayMedia API w3c/mediacapture-screen-share#300.
-
getUserMedia media streams capturing issue in MV3 (chrome extension) with respect to constraints w3c/mediacapture-screen-share#299.
-
Inconsistent formatting in doc w3c/mediacapture-screen-share#234.
-
Use a single enum for or all w3c/mediacapture-screen-share#277.
-
getUserMedia media streams capturing issue in MV3 (chrome extension) with respect to constraints w3c/mediacapture-screen-share#296.
-
Spec should make use of https://w3c.github.io/mediacapture-main/#dfn-create-a-mediastreamtrack to create MediaStreamTrack w3c/mediacapture-screen-share#293.
-
-
9 issues received 14 new comments.
-
Detect when minimizing a window pauses capture (was: Capability polling - capture-while-minimized) w3c/mediacapture-screen-share#257 (3 comments by @jan-ivar, @youennf)
-
Distinguish cancellations from absent OS permissions w3c/mediacapture-screen-share#281 (3 comments by @dontcallmedom-bot, @jan-ivar)
-
Should we have a screenshare extension spec? w3c/mediacapture-screen-share#297 (2 comments by @dontcallmedom-bot, @eladalon1983)
-
Want to restrict the options of the getDisplayMedia API w3c/mediacapture-screen-share#300 (1 comment by @dontcallmedom)
-
getUserMedia media streams capturing issue in MV3 (chrome extension) with respect to constraints w3c/mediacapture-screen-share#299 (1 comment by @dontcallmedom)
-
getUserMedia media streams capturing issue in MV3 (chrome extension) with respect to constraints w3c/mediacapture-screen-share#296 (1 comment by @jan-ivar)
-
-
1 pull request merged.
-
Explicitly create MediaStream tracks in getDisplayMedia algorithm w3c/mediacapture-screen-share#294.
-
-
1 pull request received 1 new comment.
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Should we add captureTimestamp senderCaptureTimeOffset to the RTCEncodedXXXFrameMetadata if abs-capture-time is used? w3c/webrtc-encoded-transform#225, by @murillo128.
-
-
1 issue received 1 new comment.
-
Should we add captureTimestamp senderCaptureTimeOffset to the RTCEncodedXXXFrameMetadata if abs-capture-time is used? w3c/webrtc-encoded-transform#225 (1 comment by @tonyherre)
-
-
1 pull request opened.
-
Add explainer for a congestion control API proposal w3c/webrtc-encoded-transform#224, by @alvestrand.
-
-
1 pull request received 2 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (2 comments by @alvestrand, @dontcallmedom-bot)
-
w3c/webrtc-pc
-
10 issues opened.
-
Alternative storage for RTCCertificates needed w3c/webrtc-pc#2944, by @steely-glint.
-
Review mute/unmute/ended and constraints on RTCRtpReceiver's track. w3c/webrtc-pc#2942, by @jan-ivar.
-
RTCSessionDescriptionInit vs "local" RTCLocalSessionDescriptionInit w3c/webrtc-pc#2940, by @jarrodcolburn.
-
Proposing setCodecPreferences to deal with both send and recv codecs w3c/webrtc-pc#2939, by @henbos.
-
If a preferred codec is filtered out, does it still get assigned a PT? w3c/webrtc-pc#2938, by @henbos.
-
setCodecPreferences, sendonly codecs and dummy codecs w3c/webrtc-pc#2937, by @henbos.
-
Existing setCodecPreferences NOTE is wrong and should be deleted w3c/webrtc-pc#2933, by @henbos.
-
Clarify a=rtpmap codec mappings should be offered even if the codec is not a preferred one w3c/webrtc-pc#2932, by @henbos.
-
5 issues closed.
-
Modify the codec description model to ease describing changes w3c/webrtc-pc#2925.
-
Existing setCodecPreferences NOTE is wrong and should be deleted w3c/webrtc-pc#2933.
-
Is it illegal to modify sdp between createOffer and setLocalDescription? w3c/webrtc-pc#2907.
-
-
2 issues reopened.
-
Clarify a=rtpmap codec mappings should be offered even if the codec is not a preferred one w3c/webrtc-pc#2932, by @henbos.
-
Clarify a=rtpmap codec mappings should be offered even if the codec is not a preferred one w3c/webrtc-pc#2932, by @henbos.
-
-
12 issues received 111 new comments.
-
Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel w3c/webrtc-pc#2931 (28 comments by @aboba, @alvestrand, @caribouW3, @cdh4u, @dontcallmedom, @gunnarhm, @lminiero)
-
Clarify a=rtpmap codec mappings should be offered even if the codec is not a preferred one w3c/webrtc-pc#2932 (20 comments by @alvestrand, @fippo, @henbos)
-
If a preferred codec is filtered out, does it still get assigned a PT? w3c/webrtc-pc#2938 (16 comments by @aboba, @alvestrand, @cdh4u, @dontcallmedom-bot, @fippo, @henbos, @rshpount, @stefhak)
-
setCodecPreferences, sendonly codecs and dummy codecs w3c/webrtc-pc#2937 (12 comments by @dontcallmedom-bot, @fippo, @henbos)
-
Should media capabilities influence what is exposed in what is exposed in WebRTC offers and answers w3c/webrtc-pc#2929 (9 comments by @alvestrand, @dontcallmedom-bot, @youennf)
-
Existing setCodecPreferences NOTE is wrong and should be deleted w3c/webrtc-pc#2933 (8 comments by @alvestrand, @dontcallmedom-bot, @fippo, @henbos)
-
Specify what should happen if filtering [[PreferredCodecs]] on direction results in empty list w3c/webrtc-pc#2936 (7 comments by @fippo, @henbos)
-
simple webrtc connection and manual signaling (QR, JSON, Carrier pigeon) - consent time out prevents connection w3c/webrtc-pc#2945 (3 comments by @fippo, @juberti, @minidogenft)
-
Proposing setCodecPreferences to deal with both send and recv codecs w3c/webrtc-pc#2939 (3 comments by @aboba, @dontcallmedom-bot, @fippo)
-
Modify the codec description model to ease describing changes w3c/webrtc-pc#2925 (2 comments by @dontcallmedom-bot, @henbos)
-
RTCSessionDescriptionInit vs "local" RTCLocalSessionDescriptionInit w3c/webrtc-pc#2940 (1 comment by @jan-ivar)
-
-
4 pull requests opened.
-
Rebase PR onto main w3c/webrtc-pc#2943, by @alvestrand.
-
remove setCodecPreferences note already covered by JSEP w3c/webrtc-pc#2941, by @fippo.
-
Redefine SendCodecs and ReceiveCodecs w3c/webrtc-pc#2935, by @alvestrand.
-
Update to ReSpec version 34.4.0 w3c/webrtc-pc#2934, by @dontcallmedom.
-
-
5 pull requests merged.
-
Redefine SendCodecs and ReceiveCodecs w3c/webrtc-pc#2935.
-
remove setCodecPreferences note already covered by JSEP w3c/webrtc-pc#2941.
-
add test coverage annotation for sdp munging w3c/webrtc-pc#2928.
-
make setCodecPreferences only look at receive codecs w3c/webrtc-pc#2926.
-
Update to ReSpec version 34.4.0 w3c/webrtc-pc#2934.
-
-
1 pull request closed.
-
Rebase PR onto main w3c/webrtc-pc#2943.
-
-
2 pull requests received 26 new comments.
-
Redefine SendCodecs and ReceiveCodecs w3c/webrtc-pc#2935 (17 comments by @alvestrand, @dontcallmedom, @dontcallmedom-bot, @jan-ivar)
-
make setCodecPreferences only look at receive codecs w3c/webrtc-pc#2926 (9 comments by @alvestrand, @dontcallmedom, @dontcallmedom-bot, @fippo, @henbos)
-
w3c/webrtc-stats
-
1 issue opened.
-
Should RTCRtptransceiver.stop() cause inbound-rtp stats to disappear? w3c/webrtc-stats#784, by @jan-ivar.
-
-
1 pull request opened.
-
raddr+rport can be set for peer-reflexive candidates as well w3c/webrtc-stats#783, by @fippo.
-
w3c/mediacapture-record
-
1 issue closed.
-
Edge cases related to firing start and stop events w3c/mediacapture-record#204.
-
-
3 issues received 5 new comments.
-
mimeType ambiguity: "video/webm;codecs=vp8" means? w3c/mediacapture-record#194 (2 comments by @jan-ivar)
-
deprecate isTypeSupported (was: MediaRecorder specification expects to synchronously know the list of supported mime types) w3c/mediacapture-record#202 (2 comments by @dontcallmedom-bot, @jan-ivar)
-
Ability to record non-realtime / frame-by-frame w3c/mediacapture-record#213 (1 comment by @dontcallmedom-bot)
-
w3c/webrtc-extensions
-
1 issue opened.
-
Add jitterBufferMaximumDelay attribute to RTCRtpReceiver w3c/webrtc-extensions#199, by @eldarrello.
-
-
1 issue closed.
-
Maintain an internal slot of candidate pairs that are valid inputs to RTCIceTransport operations w3c/webrtc-extensions#188.
-
-
3 issues received 10 new comments.
-
Peer Connection and back/forward cache w3c/webrtc-extensions#200 (5 comments by @aboba, @docfaraday, @fippo, @jan-ivar, @youennf)
-
Add jitterBufferMaximumDelay attribute to RTCRtpReceiver w3c/webrtc-extensions#199 (4 comments by @alvestrand, @eldarrello)
-
-
1 pull request opened.
-
Add RTCRtpEncodedSource and explainer w3c/webrtc-extensions#198, by @guidou.
-
-
1 pull request merged.
-
Add an internal slot for active candidate pairs (re-upload) w3c/webrtc-extensions#197.
-
w3c/mediacapture-extensions
-
1 issue opened.
-
Moving the source of a track w3c/mediacapture-extensions#139, by @alvestrand.
-
-
1 issue closed.
-
Clarify how `track.stats.resetLatency()` relates to run-to-completion semantics w3c/mediacapture-extensions#136.
-
-
2 issues received 4 new comments.
-
Detecting user-actionable camera issues (e.g., camera shutters) w3c/mediacapture-extensions#140 (2 comments by @fippo, @jan-ivar)
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (2 comments by @RomanKiryanov, @suzukieng)
-
-
1 pull request merged.
-
Clarify how resetLatency() relates to run-to-completion semantics. w3c/mediacapture-extensions#137.
-
-
1 pull request reopened.
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83, by @jan-ivar.
-
-
2 pull requests received 5 new comments.
-
Expose MediaStream in workers w3c/mediacapture-extensions#26 (3 comments by @dontcallmedom-bot, @jan-ivar)
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83 (2 comments by @jan-ivar)
-
w3c/mediacapture-fromelement
-
2 issues opened.
-
Review mute/unmute/ended and constraints on tracks from canvas.captureStream() w3c/mediacapture-fromelement#99, by @jan-ivar.
-
Review mute/unmute/ended and constraints on tracks from element.captureStream() w3c/mediacapture-fromelement#98, by @jan-ivar.
-
-
1 issue received 1 new comment.
w3c/mediacapture-transform
-
2 issues opened.
-
Review mute/unmute/ended and constraints on new VideoTrackGenerator().track w3c/mediacapture-transform#109, by @jan-ivar.
-
Spec is unclear when and how WebCodecs VideoFrame objects are created w3c/mediacapture-transform#106, by @youennf.
-
-
5 issues closed.
-
Spec is unclear when and how WebCodecs VideoFrame objects are created w3c/mediacapture-transform#106.
-
UAs should be allowed to clamp maxBufferSize w3c/mediacapture-transform#95.
-
Writing a closed video frame to VideoTrackGenerator.writable should fail w3c/mediacapture-transform#100.
-
Add a Makefile to locally build the spec from bikeshed w3c/mediacapture-transform#99.
-
Spec should link to https://www.w3.org/TR/webcodecs/#close-videoframe instead of calling close() w3c/mediacapture-transform#91.
-
-
1 issue received 1 new comment.
-
Review mute/unmute/ended and constraints on new VideoTrackGenerator().track w3c/mediacapture-transform#109 (1 comment by @jan-ivar)
-
-
2 pull requests opened.
-
Explicitly clone/close VideoFrames in generator and processor w3c/mediacapture-transform#108, by @youennf.
-
Update Detached slot to link to html spec. w3c/mediacapture-transform#107, by @youennf.
-
-
8 pull requests merged.
-
Explicitly clone/close VideoFrames in generator and processor w3c/mediacapture-transform#108.
-
Update Detached slot to link to html spec. w3c/mediacapture-transform#107.
-
Allow UA to clamp maxBufferSize to a value between 1 and the value provided by the web page w3c/mediacapture-transform#105.
-
Writing a closed video frame should reject w3c/mediacapture-transform#101.
-
Add a note stating that audio MediaStreamTrackProcessor has not reached consensus w3c/mediacapture-transform#104.
-
Add makefile to locally build the bs spec w3c/mediacapture-transform#103.
-
Call VideoFrame Close algorithm instead of VideoFrame close method w3c/mediacapture-transform#102.
-
Fix two typo w3c/mediacapture-transform#98.
-
-
3 pull requests received 8 new comments.
-
Allow UA to clamp maxBufferSize to a value between 1 and the value provided by the web page w3c/mediacapture-transform#105 (6 comments by @alvestrand, @henbos, @youennf)
-
Explicitly clone/close VideoFrames in generator and processor w3c/mediacapture-transform#108 (1 comment by @youennf)
-
w3c/mediacapture-surface-control
-
2 issues opened.
-
Should getSupportedZoomLevels() be static? w3c/mediacapture-surface-control#8, by @eladalon1983.
-
Should the deltas be called deltaX/deltaY? w3c/mediacapture-surface-control#5, by @eladalon1983.
-
-
1 issue received 2 new comments.
-
What value should `Event.isTrusted` have? w3c/mediacapture-surface-control#1 (2 comments by @eladalon1983)
-
-
4 pull requests opened.
-
Fix nits in README.md w3c/mediacapture-surface-control#9, by @beaufortfrancois.
-
Update translateCoordinates helper function w3c/mediacapture-surface-control#7, by @beaufortfrancois.
-
Update README.md w3c/mediacapture-surface-control#6, by @eladalon1983.
-
Fix reference to deprecate delta fields w3c/mediacapture-surface-control#4, by @eladalon1983.
-
-
3 pull requests merged.
-
Fix nits in README.md w3c/mediacapture-surface-control#9.
-
Update translateCoordinates helper function w3c/mediacapture-surface-control#7.
-
Fix reference to deprecate delta fields w3c/mediacapture-surface-control#4.
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 1 new comment.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (1 comment by @eladalon1983)
-
w3c/mediacapture-handle
-
1 issue opened.
-
URL-based Screen Share Restriction? w3c/mediacapture-handle#73, by @michhyun1.
-
-
1 issue received 3 new comments.
-
URL-based Screen Share Restriction? w3c/mediacapture-handle#73 (3 comments by @eladalon1983, @michhyun1)
-
w3c/webrtc-svc
-
1 pull request merged.
-
Rewrite of Privacy Considerations Section w3c/webrtc-svc#101.
-
TR publications
-
3 documents published.
-
Identifiers for WebRTC's Statistics API published twice as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Scalable Video Coding (SVC) Extension for WebRTC published as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Tony Herre (Google LLC) joined.
-
-
1 participant left.
-
Antoine Dumas (Preset Computing) left.
-
-
1 organization left.
-
Preset Computing left.
-
GitHub
w3c/webrtc-pc
-
10 issues opened.
-
Consider making RTCIceCandidatePair an interface w3c/webrtc-pc#2930, by @jan-ivar.
-
Applying a remote offer with unsupported codecs results in stale transceiver w3c/webrtc-pc#2927, by @mickel8.
-
Modify the codec description model to ease describing changes w3c/webrtc-pc#2925, by @alvestrand.
-
QUIC as Transport for Session Traversal Utilities for NAT (STUN) w3c/webrtc-pc#2924, by @hakarim740-com-ra.
-
Adding and stopping transceiver before first offer will result in unremovable transceiver w3c/webrtc-pc#2923, by @mickel8.
-
Clarify simulcast envelope is a sender property w3c/webrtc-pc#2921, by @jan-ivar.
-
support for alpha channel when transferring canvas. w3c/webrtc-pc#2920, by @jimmywarting.
-
8 issues closed.
-
what error is thrown for an SDP without a a=fingerprint attribute w3c/webrtc-pc#2672.
-
is addTrack(track, stream, stream) allowed? w3c/webrtc-pc#2803.
-
Clarify simulcast envelope is a sender property w3c/webrtc-pc#2921.
-
data channel default binaryType value is 'blob' w3c/webrtc-pc#2170.
-
22 issues received 69 new comments.
-
Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel w3c/webrtc-pc#2931 (9 comments by @aboba, @alvestrand, @brtech99, @cdh4u, @gunnarhm)
-
Changing RTCRtpTransceiver direction from recvonly to sendrecv on the answerer side doesn't fire negotiationneeded event w3c/webrtc-pc#2919 (9 comments by @alvestrand, @fippo, @mickel8)
-
setCodecPreferences vs unidirectional codecs w3c/webrtc-pc#2888 (8 comments by @alvestrand, @fippo, @henbos, @Orphis, @stefhak)
-
WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track receiving mute/unmute w3c/webrtc-pc#2915 (5 comments by @fippo, @henbos, @jan-ivar, @youennf)
-
Should media capabilities influence what is exposed in what is exposed in WebRTC offers and answers w3c/webrtc-pc#2929 (4 comments by @aboba, @alvestrand, @youennf)
-
TURN servers running over webtransport w3c/webrtc-pc#2651 (4 comments by @hakarim740-com-ra, @juberti, @murillo128)
-
support for alpha channel when transferring canvas. w3c/webrtc-pc#2920 (4 comments by @fippo, @jimmywarting, @rosetta-jpn)
-
Modify the codec description model to ease describing changes w3c/webrtc-pc#2925 (3 comments by @alvestrand, @fippo)
-
Adding and stopping transceiver before first offer will result in unremovable transceiver w3c/webrtc-pc#2923 (3 comments by @fippo, @mickel8)
-
QUIC as Transport for Session Traversal Utilities for NAT (STUN) w3c/webrtc-pc#2924 (3 comments by @alvestrand, @hakarim740-com-ra)
-
Is it illegal to modify sdp between createOffer and setLocalDescription? w3c/webrtc-pc#2907 (2 comments by @fippo, @henbos)
-
Applying a remote offer with unsupported codecs results in stale transceiver w3c/webrtc-pc#2927 (2 comments by @fippo, @mickel8)
-
what error is thrown for an SDP without a a=fingerprint attribute w3c/webrtc-pc#2672 (2 comments by @fippo, @pthatcher)
-
maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders w3c/webrtc-pc#2815 (2 comments by @henbos, @Orphis)
-
Clarify unmute event must fire on receiver.track AFTER sRD(offer) succeeds w3c/webrtc-pc#2880 (2 comments by @alvestrand, @mickel8)
-
Should RTCRtpTransceiver.setCodecPreferences() only refer to RTCRtpReceiver.getCapabilities(kind)? w3c/webrtc-pc#1998 (1 comment by @alvestrand)
-
Transceivers stopped prior to being negotiated are never removed from the set of transcievers w3c/webrtc-pc#2838 (1 comment by @alvestrand)
-
Why is RTCIceCandidatePairStats.totalRoundTripTime mandatory to implement, but not responsesReceived? w3c/webrtc-pc#2819 (1 comment by @fippo)
-
-
3 pull requests opened.
-
add test coverage annotation for sdp munging w3c/webrtc-pc#2928, by @fippo.
-
make setCodecPreferences only look at receive codecs w3c/webrtc-pc#2926, by @fippo.
-
Move Simulcast envelope concept to RTCRtpSender. w3c/webrtc-pc#2922, by @jan-ivar.
-
-
2 pull requests merged.
-
Move Simulcast envelope concept to RTCRtpSender. w3c/webrtc-pc#2922.
-
Update to ReSpec version 34.3.0 w3c/webrtc-pc#2918.
-
-
3 pull requests received 4 new comments.
-
make setCodecPreferences only look at receive codecs w3c/webrtc-pc#2926 (2 comments by @fippo, @stefhak)
-
w3c/webrtc-stats
-
4 issues opened.
-
Lifetime of outbound-rtp should start BEFORE first packet is sent w3c/webrtc-stats#781, by @henbos.
-
Is codec.sdpFmtpLine present when there is no fmtp line in the SDP? w3c/webrtc-stats#779, by @fippo.
-
Make "not present" reference "map/exist" w3c/webrtc-stats#776, by @henbos.
-
Change "Does not" to "must not" w3c/webrtc-stats#775, by @henbos.
-
-
3 issues closed.
-
Is codec.sdpFmtpLine present when there is no fmtp line in the SDP? w3c/webrtc-stats#779.
-
Make "not present" reference "map/exist" w3c/webrtc-stats#776.
-
Change "Does not" to "must not" w3c/webrtc-stats#775.
-
-
2 issues received 5 new comments.
-
Lifetime of outbound-rtp should start BEFORE first packet is sent w3c/webrtc-stats#781 (3 comments by @fippo, @henbos)
-
Is codec.sdpFmtpLine present when there is no fmtp line in the SDP? w3c/webrtc-stats#779 (2 comments by @alvestrand, @fippo)
-
-
4 pull requests opened.
-
sync local-candidate url definition with webrtc-pc w3c/webrtc-stats#782, by @fippo.
-
clarify that sdpFmtpLine may not be there w3c/webrtc-stats#780, by @fippo.
-
Replace 'is not present' with 'MUST NOT be [= map/exist | present =]' w3c/webrtc-stats#778, by @henbos.
-
Replace 'Does not map/exist' with 'MUST NOT map/exist' w3c/webrtc-stats#777, by @henbos.
-
-
4 pull requests merged.
-
clarify that sdpFmtpLine may not be there w3c/webrtc-stats#780.
-
Replace 'is not present' with 'MUST NOT be [= map/exist | present =]' w3c/webrtc-stats#778.
-
Replace 'Does not map/exist' with 'MUST NOT map/exist' w3c/webrtc-stats#777.
-
Add "only exists" clause to various audio/video stats w3c/webrtc-stats#774.
-
-
4 pull requests received 17 new comments.
-
Add "only exists" clause to various audio/video stats w3c/webrtc-stats#774 (13 comments by @fippo, @henbos, @jan-ivar)
-
Replace 'is not present' with 'MUST NOT be [= map/exist | present =]' w3c/webrtc-stats#778 (1 comment by @henbos)
-
w3c/mediacapture-main
-
2 issues opened.
-
The [=muted=] concept is exported wrongly w3c/mediacapture-main#985, by @youennf.
-
Clarify each source is responsible for specifying mute/unmute/ended and constraints behavior w3c/mediacapture-main#984, by @jan-ivar.
-
-
1 issue closed.
-
Transformation of camera signal into displayed frames on screen in a video capture pipeline. w3c/mediacapture-main#981.
-
-
5 issues received 17 new comments.
-
Avoid circular definition of muted. w3c/mediacapture-main#982 (7 comments by @alvestrand, @eladalon1983, @guidou, @youennf)
-
Mark sampleRate, sampleSize, latency as features at risk w3c/mediacapture-main#958 (5 comments by @guidou, @jan-ivar, @youennf)
-
How should MediaStreamTrack interact with BFCache? w3c/mediacapture-main#974 (3 comments by @fergald, @jan-ivar, @youennf)
-
Transformation of camera signal into displayed frames on screen in a video capture pipeline. w3c/mediacapture-main#981 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Add guidance for defining a new source of MediaStreamTrack w3c/mediacapture-main#988, by @jan-ivar.
-
Mark sampleRate, sampleSize, and latency are at risk w3c/mediacapture-main#987, by @jan-ivar.
-
Fix export of track-muted and set-track-muted. w3c/mediacapture-main#986, by @jan-ivar.
-
-
1 pull request merged.
-
Update to latest ReSpec version 34.3.0 w3c/mediacapture-main#983.
-
-
1 pull request received 3 new comments.
-
Fix export of track-muted and set-track-muted. w3c/mediacapture-main#986 (3 comments by @jan-ivar, @youennf)
-
w3c/mediacapture-record
-
1 issue opened.
-
Is the project still maintained? w3c/mediacapture-record#221, by @marwa-abdallah.
-
-
4 issues closed.
-
Is the project still maintained? w3c/mediacapture-record#221.
-
isTypeSupported() algorithm should be more specific w3c/mediacapture-record#92.
-
Reconsider isTypeSupported() API w3c/mediacapture-record#93.
-
The changes in the canvas are not being recognized correctly. w3c/mediacapture-record#218.
-
-
4 issues received 4 new comments.
-
isTypeSupported() algorithm should be more specific w3c/mediacapture-record#92 (1 comment by @jan-ivar)
-
The changes in the canvas are not being recognized correctly. w3c/mediacapture-record#218 (1 comment by @jan-ivar)
-
w3c/webrtc-encoded-transform
-
2 issues opened.
-
Should RTCRtpTransceiverInit have sendTransform and receiveTransform members? w3c/webrtc-encoded-transform#221, by @jan-ivar.
-
Is RTCEncodedVideoFrameMetadata.frame_id actually an unsigned long long or does it wrap at 16 bits? w3c/webrtc-encoded-transform#220, by @tonyherre.
-
-
1 issue closed.
-
Is RTCEncodedVideoFrameMetadata.frame_id actually an unsigned long long or does it wrap at 16 bits? w3c/webrtc-encoded-transform#220.
-
-
2 issues received 8 new comments.
-
Is RTCEncodedVideoFrameMetadata.frame_id actually an unsigned long long or does it wrap at 16 bits? w3c/webrtc-encoded-transform#220 (7 comments by @aboba, @alvestrand, @fippo, @tonyherre)
-
width/height metadata on incoming streams w3c/webrtc-encoded-transform#138 (1 comment by @alvestrand)
-
-
2 pull requests opened.
-
Constructor frame w3c/webrtc-encoded-transform#223, by @guidou.
-
Add definition of RTCEncodedVideoFrameMetadata frameId and dependencies w3c/webrtc-encoded-transform#222, by @tonyherre.
-
-
2 pull requests merged.
-
Add definition of RTCEncodedVideoFrameMetadata frameId and dependencies w3c/webrtc-encoded-transform#222.
-
Editorial: Use AbortController/signal to access controller's signal w3c/webrtc-encoded-transform#190.
-
-
2 pull requests received 25 new comments.
-
Add definition of RTCEncodedVideoFrameMetadata frameId and dependencies w3c/webrtc-encoded-transform#222 (16 comments by @alvestrand, @fippo, @tonyherre)
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (9 comments by @alvestrand, @jan-ivar)
-
w3c/mediacapture-transform
-
9 issues opened.
-
Writing a closed video frame to VideoTrackGenerator.writable should fail w3c/mediacapture-transform#100, by @youennf.
-
Add a Makefile to locally build the spec from bikeshed w3c/mediacapture-transform#99, by @youennf.
-
VideoTrackGenerator.applyConstraints success is unclear w3c/mediacapture-transform#97, by @youennf.
-
What is the impact of timestamp for video frames enqueued in VideoTrackGenerator? w3c/mediacapture-transform#96, by @youennf.
-
UAs should be allowed to clamp maxBufferSize w3c/mediacapture-transform#95, by @youennf.
-
What is a valid MediaStreamTrack w3c/mediacapture-transform#94, by @youennf.
-
What happens when the MediaStreamTrack of the VideoTrackGenerator (and all its clones) get stopped? w3c/mediacapture-transform#93, by @youennf.
-
Should we document in the spec that there is no consensus on whether supporting MediaStreamTrackProcessor for audio? w3c/mediacapture-transform#92, by @youennf.
-
Spec should link to https://www.w3.org/TR/webcodecs/#close-videoframe instead of calling close() w3c/mediacapture-transform#91, by @youennf.
-
-
2 issues closed.
-
What happens when the MediaStreamTrack of the VideoTrackGenerator (and all its clones) get stopped? w3c/mediacapture-transform#93.
-
How does generator.mute change track states? w3c/mediacapture-transform#81.
-
-
6 issues received 11 new comments.
-
Should we document in the spec that there is no consensus on whether supporting MediaStreamTrackProcessor for audio? w3c/mediacapture-transform#92 (6 comments by @guidou, @youennf)
-
Is MediaStreamTrackProcessor for audio necessary? w3c/mediacapture-transform#29 (1 comment by @guidou)
-
What is the impact of timestamp for video frames enqueued in VideoTrackGenerator? w3c/mediacapture-transform#96 (1 comment by @youennf)
-
What happens when the MediaStreamTrack of the VideoTrackGenerator (and all its clones) get stopped? w3c/mediacapture-transform#93 (1 comment by @youennf)
-
How does generator.mute change track states? w3c/mediacapture-transform#81 (1 comment by @alvestrand)
-
-
7 pull requests opened.
-
Allow UA to clamp maxBufferSize to a value between 1 and the value provided by the web page w3c/mediacapture-transform#105, by @youennf.
-
Add a note stating that audio MediaStreamTrackProcessor has not reached consensus w3c/mediacapture-transform#104, by @youennf.
-
Add makefile to locally build the bs spec w3c/mediacapture-transform#103, by @youennf.
-
Call VideoFrame Close algorithm instead of VideoFrame close method w3c/mediacapture-transform#102, by @youennf.
-
Writing a closed video frame should reject w3c/mediacapture-transform#101, by @youennf.
-
Fix two typo w3c/mediacapture-transform#98, by @youennf.
-
Make MediaStreamTrackProcessor.readable readonly w3c/mediacapture-transform#90, by @youennf.
-
-
1 pull request merged.
-
Make MediaStreamTrackProcessor.readable readonly w3c/mediacapture-transform#90.
-
-
1 pull request received 1 new comment.
-
Call VideoFrame Close algorithm instead of VideoFrame close method w3c/mediacapture-transform#102 (1 comment by @youennf)
-
w3c/webrtc-extensions
-
2 issues opened.
-
Add steps to clear [[CandidatePairs]] in response to ICE restart w3c/webrtc-extensions#196, by @henbos.
-
How is RTCRtpCodec codec used? w3c/webrtc-extensions#195, by @stefhak.
-
-
3 issues closed.
-
Describe a match algorithm for two RTCIceCandidatePairs w3c/webrtc-extensions#187.
-
ICE improvements: remove candidate pairs w3c/webrtc-extensions#170.
-
Describe a match algorithm for two RTCIceCandidates w3c/webrtc-extensions#186.
-
-
2 issues received 5 new comments.
-
Add API to control encode complexity w3c/webrtc-extensions#191 (4 comments by @fippo, @Orphis, @youennf)
-
-
2 pull requests opened.
-
Add an internal slot for active candidate pairs (re-upload) w3c/webrtc-extensions#197, by @henbos.
-
Add an internal slot for active candidate pairs. w3c/webrtc-extensions#194, by @sam-vi.
-
-
3 pull requests merged.
-
Define a candidate pair match algorithm. w3c/webrtc-extensions#193.
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175.
-
Define an RTCIceCandidate match algorithm. w3c/webrtc-extensions#192.
-
-
1 pull request closed.
-
Add an internal slot for active candidate pairs. w3c/webrtc-extensions#194.
-
-
3 pull requests received 25 new comments.
-
Add an internal slot for active candidate pairs. w3c/webrtc-extensions#194 (13 comments by @alvestrand, @henbos, @jan-ivar)
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175 (11 comments by @henbos, @jan-ivar, @sam-vi)
-
w3c/mediacapture-screen-share
-
3 issues opened.
-
Should we have a screenshare extension spec? w3c/mediacapture-screen-share#297, by @youennf.
-
getUserMedia media streams capturing issue in MV3 (chrome extension) with respect to constraints w3c/mediacapture-screen-share#296, by @Nitesh2503.
-
Spec should make use of https://w3c.github.io/mediacapture-main/#dfn-create-a-mediastreamtrack to create MediaStreamTrack w3c/mediacapture-screen-share#293, by @youennf.
-
-
4 issues closed.
-
Can I share some Windows? w3c/mediacapture-screen-share#280.
-
Can a shared surface select its derivative window？ w3c/mediacapture-screen-share#282.
-
Should pending getDisplayMedia() calls reject on sleep and/or screen-lock? w3c/mediacapture-screen-share#287.
-
Multiple screen capture w3c/mediacapture-screen-share#292.
-
-
7 issues received 20 new comments.
-
Distinguish cancellations from absent OS permissions w3c/mediacapture-screen-share#281 (10 comments by @eladalon1983, @jan-ivar, @youennf)
-
Spec should make use of https://w3c.github.io/mediacapture-main/#dfn-create-a-mediastreamtrack to create MediaStreamTrack w3c/mediacapture-screen-share#293 (3 comments by @alvestrand, @youennf)
-
Should we have a screenshare extension spec? w3c/mediacapture-screen-share#297 (2 comments by @jan-ivar, @youennf)
-
Can a shared surface select its derivative window？ w3c/mediacapture-screen-share#282 (1 comment by @jan-ivar)
-
Should pending getDisplayMedia() calls reject on sleep and/or screen-lock? w3c/mediacapture-screen-share#287 (1 comment by @jan-ivar)
-
-
1 pull request opened.
-
Explicitly create MediaStream tracks in getDisplayMedia algorithm w3c/mediacapture-screen-share#294, by @youennf.
-
-
1 pull request received 1 new comment.
-
Explicitly create MediaStream tracks in getDisplayMedia algorithm w3c/mediacapture-screen-share#294 (1 comment by @youennf)
-
w3c/webrtc-svc
-
4 pull requests opened.
-
Rewrite of Privacy Considerations Section w3c/webrtc-svc#101, by @aboba.
-
Aboba patch 12 w3c/webrtc-svc#100, by @aboba.
-
Rewrite of Privacy Considerations Section w3c/webrtc-svc#99, by @aboba.
-
Use canonical AV1-RTP-SPEC reference w3c/webrtc-svc#98, by @fippo.
-
-
2 pull requests merged.
-
Rewrite of Privacy Considerations Section w3c/webrtc-svc#99.
-
Use canonical AV1-RTP-SPEC reference w3c/webrtc-svc#98.
-
-
2 pull requests closed.
-
Aboba patch 12 w3c/webrtc-svc#100.
-
Rewrite of Privacy Considerations Section w3c/webrtc-svc#97.
-
-
1 pull request received 1 new comment.
w3c/mediacapture-extensions
-
2 issues opened.
-
Clarify how `track.stats.resetLatency()` relates to run-to-completion semantics w3c/mediacapture-extensions#136, by @henbos.
-
4 issues received 7 new comments.
-
Transferable MediaStreamTrack: Within Agent Cluster or between Agent Clusters? w3c/mediacapture-extensions#43 (4 comments by @alvestrand, @youennf)
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (1 comment by @ivancuric)
-
Clarify how `track.stats.resetLatency()` relates to run-to-completion semantics w3c/mediacapture-extensions#136 (1 comment by @henbos)
-
Echo cancellation: Need to specify the source of the echo cancellation reference signal w3c/mediacapture-extensions#31 (1 comment by @alvestrand)
-
-
1 pull request opened.
-
Clarify how resetLatency() relates to run-to-completion semantics. w3c/mediacapture-extensions#137, by @henbos.
-
-
1 pull request received 2 new comments.
-
Clarify how resetLatency() relates to run-to-completion semantics. w3c/mediacapture-extensions#137 (2 comments by @henbos)
-
w3c/mediacapture-automation
-
1 issue opened.
-
Broken references in Media Capture Automation w3c/mediacapture-automation#4, by @dontcallmedom-bot.
-
w3c/mediacapture-screen-share-extensions
-
1 issue opened.
-
Want to restrict the options of the getDisplayMedia API w3c/mediacapture-screen-share-extensions#1, by @Nitesh2503.
-
-
2 issues received 5 new comments.
-
Want to restrict the options of the getDisplayMedia API w3c/mediacapture-screen-share-extensions#1 (3 comments by @beaufortfrancois, @eladalon1983, @fippo)
-
Prevent unintentional leaks w3c/mediacapture-screen-share-extensions#6 (2 comments by @NDevTK, @shreyaskaundinya)
-
w3c/mediacapture-surface-control
-
2 pull requests opened.
-
Update README.md w3c/mediacapture-surface-control#3, by @eladalon1983.
-
Improve explainer - permissions, scrolling w3c/mediacapture-surface-control#2, by @eladalon1983.
-
-
2 pull requests merged.
-
Update README.md w3c/mediacapture-surface-control#3.
-
Improve explainer - permissions, scrolling w3c/mediacapture-surface-control#2.
-
w3c/webrtc-nv-use-cases
-
1 issue closed.
-
Support for End to End Encryption (E2EE) w3c/webrtc-nv-use-cases#76.
-
-
2 issues received 3 new comments.
-
Support for End to End Encryption (E2EE) w3c/webrtc-nv-use-cases#76 (2 comments by @fluffy, @jan-ivar)
-
-
2 pull requests received 2 new comments.
-
Section 3.2.1: Add N49 - video decoding recovery after packet loss w3c/webrtc-nv-use-cases#129 (1 comment by @xingri)
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (1 comment by @xingri)
-
w3c/mst-content-hint
-
1 issue received 1 new comment.
-
1 pull request received 1 new comment.
w3c/mediacapture-output
-
1 issue received 1 new comment.
-
Undesirable prompt from selectAudioOutput({deviceId}) if valid device removed w3c/mediacapture-output#137 (1 comment by @jan-ivar)
-
w3c/mediacapture-image
-
1 pull request closed.
-
Add support to get and set desired image format w3c/mediacapture-image#185.
-
-
1 pull request received 1 new comment.
-
Add support to get and set desired image format w3c/mediacapture-image#185 (1 comment by @alvestrand)
-
w3c/mediacapture-region
-
1 issue received 1 new comment.
-
Should we support strings in addition or in lieu of opaque identifiers? w3c/mediacapture-region#46 (1 comment by @alvestrand)
-
-
2 pull requests received 2 new comments.
-
Specify a predictable error type for unimplemented Element subtypes w3c/mediacapture-region#57 (1 comment by @alvestrand)
-
Allow cropTo() to fail due to resource limitation w3c/mediacapture-region#54 (1 comment by @alvestrand)
-