public-webrtc-logs@w3.org from January 2025 by author

Anees Iqbal via GitHub

• Re: [mediacapture-record] Creation of Seekable Files (#119) (Saturday, 4 January)

Brad Isbell via GitHub

• Re: [mediacapture-main] Should we revisit and document getUserMedia() track order? (#1028) (Saturday, 18 January)

Dominique Hazael-Massieux via GitHub

• [mediacapture-screen-share] new commits pushed by dontcallmedom (Friday, 24 January)
• Re: [mediacapture-screen-share] Editorial: Export CaptureController's internal slot definitions (#313) (Friday, 24 January)
• Closed: [webrtc-pc] Use USVString for url attributes and members (#3029) (Wednesday, 15 January)
• Re: [webrtc-pc] Use USVString for url attributes and members (#3029) (Wednesday, 15 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• [mediacapture-main] new commits pushed by dontcallmedom (Monday, 6 January)
• [webrtc-pc] new commits pushed by dontcallmedom (Monday, 6 January)

dontcallmedom-bot via GitHub

• [webrtc-pc] Missing tasks in parallel steps in WebRTC: Real-Time Communication in Browsers (#3032) (Thursday, 30 January)
• [webrtc-encoded-transform] Missing tasks in parallel steps in WebRTC Encoded Transform (#236) (Thursday, 30 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Wednesday, 22 January)
• Re: [mediacapture-surface-control] Should a web page allow to select specific types of event to be forwarded and not others (#47) (Wednesday, 22 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Wednesday, 22 January)
• Re: [mediacapture-surface-control] Consideration of proposal to support zoom in/out (#40) (Wednesday, 22 January)
• Re: [mediacapture-surface-control] Consider dropping permission and making zoomLevel an attribute (#27) (Wednesday, 22 January)
• [mediacapture-surface-control] Missing tasks in parallel steps in Captured Surface Control (#52) (Tuesday, 7 January)
• [webrtc-pc] Wrong Web IDL type for URLs in WebRTC: Real-Time Communication in Browsers (#3031) (Tuesday, 7 January)
• [webrtc-stats] Wrong Web IDL type for URLs in Identifiers for WebRTC's Statistics API (#791) (Tuesday, 7 January)
• [webrtc-identity] Wrong Web IDL type for URLs in Identity for WebRTC 1.0 (#42) (Tuesday, 7 January)

Elad Alon via GitHub

• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Friday, 31 January)
• Re: [mediacapture-surface-control] Improve forwarding behavior in the overlay case (#69) (Friday, 31 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 30 January)
• [webrtc-pc] Pull Request: Fix: Missing tasks in parallel steps (Thursday, 30 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Wednesday, 29 January)
• Closed: [mediacapture-surface-control] Missing tasks in parallel steps in Captured Surface Control (#52) (Wednesday, 29 January)
• Re: [mediacapture-surface-control] Fix: Missing tasks in parallel steps in Captured Surface Control (#68) (Wednesday, 29 January)
• Re: [mediacapture-surface-control] Fix: Missing tasks in parallel steps in Captured Surface Control (#68) (Wednesday, 29 January)
• [mediacapture-surface-control] Pull Request: Fix: Missing tasks in parallel steps in Captured Surface Control (Wednesday, 29 January)
• Re: [mediacapture-surface-control] Novel interception of input has undesirable side-effects (#67) (Wednesday, 29 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Wednesday, 29 January)
• Re: [mediacapture-main] Should applyConstraints reject when track is muted? (#1029) (Wednesday, 29 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] Pull Request: Editorial: Use exported CaptureController internal slots. (Friday, 24 January)
• [mediacapture-surface-control] Update explainer (#65) (Friday, 24 January)
• Closed: [mediacapture-surface-control] Rename `capturedzoomlevelchange` event to `zoomlevelchange` (#63) (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] Pull Request: Fix missed locations with capturedzoomlevelchange (Friday, 24 January)
• Re: [mediacapture-surface-control] Rename `capturedzoomlevelchange` event to `zoomlevelchange` (#63) (Friday, 24 January)
• Re: [mediacapture-screen-share] Editorial: Export CaptureController's internal slot definitions (#313) (Friday, 24 January)
• Re: [mediacapture-screen-share] Editorial: Export CaptureController's internal slot definitions (#313) (Friday, 24 January)
• [mediacapture-screen-share] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] Pull Request: Change getZoomLevel() into a nullable attribute (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] Pull Request: Editorial: Replace <code> with backticks (Friday, 24 January)
• [mediacapture-screen-share] Pull Request: Editorial: Export CaptureController's internal slot definitions (Friday, 24 January)
• [mediacapture-screen-share] Editorial proposal: Add extension hook (#312) (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 24 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Thursday, 23 January)
• [mediacapture-surface-control] oncapturedzoomlevelchange should fire a task (#60) (Thursday, 23 January)
• Closed: [mediacapture-surface-control] Clarify "fire a blank event" for "capturedzoomlevelchange" (#50) (Thursday, 23 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Thursday, 23 January)
• Re: [mediacapture-surface-control] Clarify capturedzoomlevelchange (#57) (Thursday, 23 January)
• Closed: [mediacapture-surface-control] Where do forwarded "wheel" events fire? (#51) (Thursday, 23 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Thursday, 23 January)
• Re: [mediacapture-surface-control] Is it important for capture control to keep captured tab from knowing it is captured? (#42) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Consider window capture (#55) (Thursday, 23 January)
• [mediacapture-surface-control] Pull Request: Replace setZoomLevel() with increase/decrease/reset methods (Thursday, 23 January)
• Re: [mediacapture-surface-control] s/capturedzoomlevelchange/zoomlevelchange (#58) (Thursday, 23 January)
• [mediacapture-surface-control] Pull Request: s/capturedzoomlevelchange/zoomlevelchange (Thursday, 23 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Consider dropping permission and making zoomLevel an attribute (#27) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Consider window capture (#55) (Thursday, 23 January)
• [mediacapture-surface-control] Pull Request: Clarify capturedzoomlevelchange (Thursday, 23 January)
• [mediacapture-surface-control] Pull Request: Clarify where wheel events fire (Thursday, 23 January)
• Re: [mediacapture-surface-control] Consider window capture (#55) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Is it important for capture control to keep captured tab from knowing it is captured? (#42) (Wednesday, 22 January)
• Re: [mediacapture-surface-control] Is it important for capture control to keep captured tab from knowing it is captured? (#42) (Wednesday, 22 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Friday, 17 January)
• Re: [mediacapture-surface-control] What about touch-based scrolling? (#54) (Thursday, 16 January)
• Re: [mediacapture-surface-control] What about touch-based scrolling? (#54) (Tuesday, 14 January)
• [mediacapture-surface-control] new commits pushed by eladalon1983 (Friday, 10 January)
• Re: [mediacapture-surface-control] Editorial: Add missing nullability (#53) (Friday, 10 January)
• [mediacapture-surface-control] Pull Request: Editorial: Add missing nullability (Friday, 10 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Friday, 10 January)

François Daoust via GitHub

• [mediacapture-surface-control] Rename `capturedzoomlevelchange` event to `zoomlevelchange` (#63) (Friday, 24 January)

guidou via GitHub

• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Thursday, 16 January)
• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Wednesday, 15 January)
• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Wednesday, 15 January)
• [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Wednesday, 15 January)
• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Monday, 13 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Monday, 13 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 10 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 10 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 10 January)

handellm via GitHub

• Re: [webrtc-extensions] Add WebRTC-specific interactions with capture/receive/RTP timestamps (#224) (Friday, 10 January)

Harald Alvestrand via GitHub

• Re: [mediacapture-main] Should applyConstraints reject when track is muted? (#1029) (Tuesday, 28 January)
• Re: [mediacapture-surface-control] Consider window capture (#55) (Thursday, 23 January)
• [webrtc-stats] Need support for statistics for L4S (#793) (Wednesday, 22 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• [webrtc-stats] Pull Request: Add counters that support deployment of L4S (Thursday, 16 January)
• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Wednesday, 15 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)

henbos via GitHub

• Re: [webrtc-rtptransport] API creates per-packet temporary objects, this is not ideal for GC (#77) (Tuesday, 21 January)
• Closed: [webrtc-rtptransport] API creates per-packet temporary objects, this is not ideal for GC (#77) (Tuesday, 21 January)
• [webrtc-rtptransport] new commits pushed by henbos (Tuesday, 21 January)
• Re: [webrtc-rtptransport] Bring Your Own Packets (#84) (Tuesday, 21 January)
• Re: [webrtc-stats] Add counters that support deployment of L4S (#792) (Friday, 17 January)
• Re: [webrtc-rtptransport] Bring Your Own Packets (#84) (Tuesday, 14 January)
• [webrtc-rtptransport] Pull Request: Bring Your Own Packets (Monday, 13 January)
• Re: [webrtc-extensions] Add WebRTC-specific interactions with capture/receive/RTP timestamps (#224) (Thursday, 9 January)
• Re: [webrtc-pc] Allow level-id to be different in codec match (#3023) (Thursday, 9 January)
• Closed: [webrtc-pc] Codec negotiation and level IDs (#3020) (Thursday, 9 January)
• [webrtc-pc] new commits pushed by henbos (Thursday, 9 January)
• Re: [webrtc-pc] Allow level-id to be different in codec match (#3023) (Thursday, 9 January)
• Re: [webrtc-pc] Allow level-id to be different in codec match (#3023) (Thursday, 9 January)
• Re: [webrtc-stats] Wrong Web IDL type for URLs in Identifiers for WebRTC's Statistics API (#791) (Tuesday, 7 January)

Jan-Ivar Bruaroey via GitHub

• Re: [mediacapture-surface-control] Improve forwarding behavior in the overlay case (#69) (Friday, 31 January)
• [mediacapture-surface-control] Improve forwarding behavior in the overlay case (#69) (Thursday, 30 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 30 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 30 January)
• [mediacapture-surface-control] Novel interception of input has undesirable side-effects (#67) (Wednesday, 29 January)
• Re: [mediacapture-main] Should we revisit and document getUserMedia() track order? (#1028) (Monday, 27 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Friday, 24 January)
• Re: [webrtc-stats] Add counters that support deployment of L4S (#792) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Is it important for capture control to keep captured tab from knowing it is captured? (#42) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Consider window capture (#55) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 23 January)
• [mediacapture-surface-control] Consider window capture (#55) (Wednesday, 22 January)
• Re: [mediacapture-surface-control] Is it important for capture control to keep captured tab from knowing it is captured? (#42) (Wednesday, 22 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Wednesday, 22 January)
• Re: [mediacapture-surface-control] Is it important for capture control to keep captured tab from knowing it is captured? (#42) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• [mediacapture-main] Should we revisit and document getUserMedia() track order? (#1028) (Friday, 17 January)
• Re: [mediacapture-main] What is the order of events being track clones? (#1020) (Friday, 17 January)
• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Friday, 17 January)
• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Friday, 17 January)
• Re: [webrtc-pc] What holds on to RTCOfferOptions and its iceRestart member (#3028) (Friday, 17 January)
• Re: [webrtc-pc] What holds on to RTCOfferOptions and its iceRestart member (#3028) (Friday, 17 January)
• Re: [mediacapture-output] Implicit consent via getUserMedia should allow access to non-miked speakers (#147) (Thursday, 16 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 16 January)
• Re: [mediacapture-surface-control] What about touch-based scrolling? (#54) (Wednesday, 15 January)
• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Wednesday, 15 January)
• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Wednesday, 15 January)
• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Wednesday, 15 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Monday, 13 January)
• Re: [mediacapture-surface-control] What about touch-based scrolling? (#54) (Monday, 13 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Monday, 13 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Monday, 13 January)
• [mediacapture-surface-control] What about touch-based scrolling? (#54) (Monday, 13 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 10 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 10 January)
• Re: [webrtc-encoded-transform] No transfer steps defined for RTCEncodedAudioFrame and RTCEncodedVideoFrame (#231) (Thursday, 9 January)
• Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45) (Thursday, 9 January)
• Re: [mediacapture-transform] Track transferability requirement adds complexity to some common use cases (#116) (Tuesday, 7 January)
• Re: [mst-content-hint] Default degradationPreference value? (#37) (Tuesday, 7 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Monday, 6 January)

Michael Hagar via GitHub

• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Monday, 13 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 3 January)

Peter Thatcher via GitHub

• Re: [webrtc-rtptransport] Bring Your Own Packets (#84) (Tuesday, 21 January)

Philipp Hancke via GitHub

• Re: [webrtc-stats] Do not expose unknown usernameFragment to stats (#789) (Friday, 3 January)

Tackoil via GitHub

• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Tuesday, 21 January)
• Re: [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Wednesday, 15 January)
• [mediacapture-main] How to interact with a device without a fixed capability? (#1027) (Monday, 13 January)

youennf via GitHub

• Re: [mediacapture-main] Should applyConstraints reject when track is muted? (#1029) (Tuesday, 28 January)
• [mediacapture-main] Should applyConstraints reject when track is muted? (#1029) (Monday, 27 January)
• Re: [mediacapture-output] Speaker devices may not always work with all microphones (#149) (Thursday, 23 January)
• [mediacapture-output] Speaker devices may not always work with all microphones (#149) (Thursday, 23 January)
• Re: [mediacapture-surface-control] Consider dropping permission and making zoomLevel an attribute (#27) (Thursday, 23 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-screen-share] Suggest User Agents treat a captured tab as visible (#307) (Tuesday, 21 January)
• Re: [mediacapture-output] allow="microphone" should authorize setSinkId (#148) (Thursday, 16 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 14 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Friday, 10 January)
• Re: [mediacapture-transform] We shouldn't require track transferability (#113) (Tuesday, 7 January)

Last message date: Friday, 31 January 2025 16:12:46 UTC