public-webrtc-logs@w3.org from May 2022 by author

Abby Yeh via GitHub

• Closed: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Thursday, 5 May)

Aziz Javed via GitHub

• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)

Bernard Aboba via GitHub

• Re: [webrtc-charter] Add link to WebTransport WG in dependencies (#66) (Tuesday, 31 May)
• Re: [webrtc-pc] webrtc-pc specifies using '~' in a=simulcast, but does not support RFC 7728 (RTP pause), which is a prerequisite (#2735) (Tuesday, 17 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Monday, 16 May)
• Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Monday, 16 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Saturday, 14 May)
• Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Friday, 13 May)
• Re: [webrtc-encoded-transform] Need APIs for using WebCodec with PeerConnection (#121) (Thursday, 12 May)
• Re: [mediacapture-transform] Support for VideoFrame <---> WebGPU translation (#84) (Sunday, 1 May)

Chuan Shao via GitHub

• Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105) (Thursday, 5 May)

docfaraday via GitHub

• [webrtc-pc] insertDTMF is synchronous, but relies on asynchronous state-checking logic (#2738) (Wednesday, 18 May)
• Re: [webrtc-pc] The prose around "simulcast envelope" falsely implies that simulcast encodings can never be removed (#2723) (Tuesday, 17 May)
• Re: [webrtc-pc] The prose around "simulcast envelope" falsely implies that simulcast encodings can never be removed (#2723) (Tuesday, 17 May)
• Re: [webrtc-pc] webrtc-pc specifies using '~' in a=simulcast, but does not support RFC 7728 (RTP pause), which is a prerequisite (#2735) (Tuesday, 17 May)
• Re: [webrtc-pc] webrtc-pc specifies using '~' in a=simulcast, but does not support RFC 7728 (RTP pause), which is a prerequisite (#2735) (Tuesday, 17 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Monday, 16 May)
• [webrtc-pc] Modifications to [[SendEncodings]] from setParameters and sRD can be racy (#2737) (Monday, 16 May)
• [webrtc-pc] webrtc-pc does not say to clear RTCRtpCodingParameters.rid when sRD rejects simulcast (#2736) (Monday, 16 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Monday, 16 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Monday, 16 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Monday, 16 May)
• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Friday, 13 May)
• [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Friday, 13 May)
• [webrtc-extensions] maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders (#107) (Wednesday, 11 May)
• Re: [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730) (Wednesday, 11 May)
• [webrtc-pc] addTransceiver does not check for missing rid properties (#2734) (Wednesday, 11 May)
• [webrtc-pc] addTransceiver does not check for uniqueness of rid (#2733) (Wednesday, 11 May)
• Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Wednesday, 11 May)
• Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Wednesday, 11 May)
• Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Wednesday, 11 May)
• [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Tuesday, 10 May)
• Re: [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730) (Tuesday, 10 May)

Domenic Denicola via GitHub

• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 18 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 6 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 5 May)

Dominique Hazael-Massieux via GitHub

• [webrtc-pc] Pull Request: Update to ReSpec version 32.1.7 (Monday, 30 May)
• [mediacapture-main] Pull Request: Update to latest ReSpec version 32.1.7 (Monday, 30 May)
• [mediacapture-main] Pull Request: Improve markup for event tables (Monday, 23 May)
• Re: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63) (Monday, 23 May)
• [mediacapture-handle] Pull Request: Fix link to editor drafts (Wednesday, 18 May)
• Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Monday, 16 May)
• Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Monday, 16 May)
• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Monday, 16 May)
• [mediacapture-handle] Pull Request: Set up Identity spec for automated updates on w3.org/TR/ (Monday, 16 May)
• [webrtc-pc] Pull Request: Update to ReSpec version 32.1.6 (Monday, 9 May)
• [mediacapture-main] Pull Request: Update to latest ReSpec version 32.1.6 (Monday, 9 May)
• [mediacapture-handle] Pull Request: Fix repo metadata in identity spec (Friday, 6 May)
• Re: [mediacapture-main] Add source specific handling for creation and cloning of tracks (#873) (Thursday, 5 May)
• Re: [webrtc-pc] Document substantive changes since Rec as candidate amendments (#2713) (Thursday, 5 May)
• Re: [webrtc-pc] Document substantive changes since Rec as candidate amendments (#2713) (Thursday, 5 May)
• Re: [webrtc-stats] transport: add dtlsRole (#629) (Wednesday, 4 May)
• [webrtc-pc] Pull Request: Clean up definitions (Monday, 2 May)
• [webrtc-pc] Pull Request: Update to ReSpec version 32.1.5 (Monday, 2 May)
• [mediacapture-main] Pull Request: Update to latest ReSpec version 32.1.5 (Monday, 2 May)

Elad Alon via GitHub

• Re: [mediacapture-region] Unsupported subtypes (#57) (Tuesday, 31 May)
• [mediacapture-region] Pull Request: Unsupported subtypes (Tuesday, 31 May)
• [mediacapture-region] Pull Request: s/throw with a new/throw a new (Tuesday, 31 May)
• [mediacapture-region] Predictable error type for unimplemented Element subtypes (#55) (Tuesday, 31 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Tuesday, 31 May)
• Re: [mediacapture-region] Allow cropTo() to fail due to resource limitation (#54) (Tuesday, 31 May)
• [mediacapture-region] Pull Request: Allow cropTo() to fail due to resource limitation (Tuesday, 31 May)
• Re: [mediacapture-region] Revert "Remove obsolete note" (#52) (Tuesday, 31 May)
• Re: [mediacapture-region] Is CropTarget name too generic? (#18) (Tuesday, 31 May)
• Re: [mediacapture-region] Remove obsolete note (name of CropTarget) (#53) (Tuesday, 31 May)
• [mediacapture-region] Pull Request: Remove obsolete note (name of CropTarget) (Tuesday, 31 May)
• [mediacapture-region] new commits pushed by eladalon1983 (Tuesday, 31 May)
• [mediacapture-region] Pull Request: Revert "Remove obsolete note" (Tuesday, 31 May)
• [mediacapture-region] new commits pushed by eladalon1983 (Tuesday, 31 May)
• Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50) (Tuesday, 31 May)
• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Monday, 30 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Monday, 30 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Monday, 30 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Saturday, 28 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 27 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 27 May)
• Re: [mediacapture-region] Clarify the cropTarget minting processing model (#47) (Friday, 27 May)
• Re: [mediacapture-region] Clarify the cropTarget minting processing model (#47) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Tuesday, 24 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50) (Tuesday, 24 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Tuesday, 24 May)
• Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 23 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Monday, 23 May)
• Re: [mediacapture-screen-share] Introduce DisplayMediaStreamConstraints.dynamicSourceOption (#225) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Monday, 23 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• [mediacapture-screen-share] Pull Request: troduce DisplayMediaStreamConstraints.dynamicSourceOption (Friday, 20 May)
• Re: [mediacapture-screen-share] Dynamic Screenshare Source (Share-this-surface-instead) (#223) (Friday, 20 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 20 May)
• [mediacapture-region] Pull Request: MediaDevices.produceCropTarget -> CropTarget.fromElement (Friday, 20 May)
• Re: [mediacapture-region] Is CropTarget name too generic? (#18) (Friday, 20 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 20 May)
• [mediacapture-region] Pull Request: Fix formatting (Friday, 20 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Friday, 20 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Friday, 20 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Friday, 20 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Friday, 20 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 20 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 18 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Wednesday, 18 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Tuesday, 17 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Tuesday, 17 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 17 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 17 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 16 May)
• Re: [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65) (Monday, 16 May)
• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Monday, 16 May)
• [mediacapture-screen-share] Pull Request: Add spec-hooks for "actively screen-capturing" (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Sunday, 15 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Sunday, 15 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Saturday, 14 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Saturday, 14 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Saturday, 14 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Saturday, 14 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-handle] Specify 1024 16-bit characters limitation in setCaptureHandleConfig (#33) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-handle] Add README file for Capture Handle Identity (#62) (Thursday, 12 May)
• Re: [mediacapture-handle] Add README file for Capture Handle Identity (#62) (Thursday, 12 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 12 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 12 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 10 May)
• Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223) (Tuesday, 10 May)
• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Tuesday, 10 May)
• Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223) (Monday, 9 May)
• Re: [mediacapture-handle] Add CaptureHandleChangeEvent removal in Changelog (#60) (Monday, 9 May)
• Closed: [mediacapture-handle] CaptureHandleChangeEvent.captureHandle() when navigating (#53) (Friday, 6 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent.captureHandle() when navigating (#53) (Friday, 6 May)
• Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55) (Friday, 6 May)
• Re: [mediacapture-handle] Add CaptureHandleChangeEvent removal in Changelog (#60) (Friday, 6 May)
• Closed: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Friday, 6 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 6 May)
• Closed: [mediacapture-screen-share] Avoid user-confusion by not offering undesired audio sources (#219) (Thursday, 5 May)
• [mediacapture-handle] Pull Request: Drop captureHandle() from the event (Tuesday, 3 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Tuesday, 3 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Tuesday, 3 May)
• Re: [mediacapture-handle] Specify event handling with algorithms (#56) (Tuesday, 3 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Tuesday, 3 May)
• Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55) (Monday, 2 May)
• Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55) (Monday, 2 May)
• [mediacapture-handle] Pull Request: Fix event.captureHandle() when not observable (Monday, 2 May)
• [mediacapture-handle] Pull Request: Fix event (Monday, 2 May)
• [mediacapture-handle] CaptureHandleChangeEvent.captureHandle() when navigating (#53) (Monday, 2 May)
• Re: [mediacapture-handle] Specify 1024 16-bit characters limitation in setCaptureHandleConfig (#33) (Monday, 2 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Monday, 2 May)

François Beaufort via GitHub

• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Friday, 20 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 18 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 18 May)
• Re: [mediacapture-handle] Add README file for Capture Handle Identity (#62) (Thursday, 12 May)
• [mediacapture-handle] Pull Request: Add wpt tests badges to README.md (Thursday, 12 May)
• [mediacapture-handle] Pull Request: Add README file for Capture Handle Identity (Thursday, 12 May)
• Re: [mediacapture-handle] Specify event handling with algorithms (#56) (Monday, 9 May)
• Re: [mediacapture-handle] Add CaptureHandleChangeEvent removal in Changelog (#60) (Monday, 9 May)
• [mediacapture-handle] Pull Request: Add CaptureHandleChangeEvent removal in Changelog (Friday, 6 May)
• [mediacapture-region] Pull Request: Remove crop ID leftovers (Thursday, 5 May)
• Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55) (Monday, 2 May)

Hamish Willee via GitHub

• Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Tuesday, 17 May)
• [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Friday, 13 May)

Harald Alvestrand via GitHub

• Re: [webrtc-pc] insertDTMF is synchronous, but relies on asynchronous state-checking logic (#2738) (Tuesday, 31 May)
• Re: [webrtc-charter] New specs (#67) (Tuesday, 31 May)
• Re: [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65) (Tuesday, 24 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 24 May)
• [webrtc-encoded-transform] Need for modifying metadata (#135) (Thursday, 19 May)
• [webrtc-encoded-transform] Need to create RTCEncodedVideoFrame from scratch (#134) (Thursday, 19 May)
• Closed: [webrtc-encoded-transform] Should we expose the precise timestamp of the frame that was triggered by a generateKeyFrame call? (#128) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 16 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Monday, 16 May)
• [mediacapture-main] Pull Request: Moving Navigator.getUserMedia to a legacy section (Monday, 16 May)
• [mediacapture-main] Legacy GetUserMedia extension is not clearly marked "informative" (#882) (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Sunday, 15 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730) (Sunday, 8 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 6 May)
• Re: [mediacapture-main] Add source specific handling for creation and cloning of tracks (#873) (Thursday, 5 May)
• Re: [mediacapture-main] Add source specific handling for creation and cloning of tracks (#873) (Thursday, 5 May)
• Re: [webrtc-stats] Remove transport.rtcpTransportStatsId (#625) (Tuesday, 3 May)
• Re: [webrtc-stats] Remove transport.rtcpTransportStatsId (#625) (Tuesday, 3 May)

henbos via GitHub

• Re: [webrtc-extensions] senderReceiverTimeOffset should use remoteOutboundRtpStats.roundTripTime (#109) (Friday, 20 May)
• [webrtc-provisional-stats] outbound-rtp.scaleResolutionDownBy (#23) (Wednesday, 18 May)
• Re: [webrtc-stats] outbound-rtp.scaleResolutionDownBy (#620) (Wednesday, 18 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)

Ian Denhardt via GitHub

• Re: [webrtc-extensions] Add a CSP check to RTCPeerConnection.addIceCandidate(). (#81) (Tuesday, 17 May)
• Re: [webrtc-extensions] Add a CSP check to RTCPeerConnection.addIceCandidate(). (#81) (Monday, 2 May)

Jan-Ivar Bruaroey via GitHub

• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Tuesday, 31 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 26 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Thursday, 26 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Saturday, 21 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Saturday, 21 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 19 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Wednesday, 18 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Wednesday, 18 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Tuesday, 17 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 17 May)
• [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65) (Monday, 16 May)
• Re: [mediacapture-region] Should cropTo be able to directly take an element as input? (#19) (Sunday, 15 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Sunday, 15 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Sunday, 15 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Sunday, 15 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Sunday, 15 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 12 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 10 May)
• Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223) (Tuesday, 10 May)
• Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223) (Monday, 9 May)
• [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730) (Friday, 6 May)
• [webrtc-pc] Improve WPT testing of setParameters (#2729) (Friday, 6 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 6 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 5 May)
• Re: [mediacapture-handle] Drop captureHandle() from the event (#57) (Thursday, 5 May)
• [mediacapture-handle] Pull Request: Replace usage of "responsible document" (Tuesday, 3 May)
• [mediacapture-handle] Pull Request: A Status of This Document must include at least one custom paragraph. (Tuesday, 3 May)
• [mediacapture-main] Pull Request: Reference relevant global object directly. (Tuesday, 3 May)
• Re: [mediacapture-handle] Specify event handling with algorithms (#56) (Tuesday, 3 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Tuesday, 3 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Tuesday, 3 May)
• Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50) (Monday, 2 May)
• [mediacapture-handle] Specify event handling with algorithms (#56) (Monday, 2 May)

Kenneth Rohde Christiansen via GitHub

• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Monday, 30 May)
• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Monday, 30 May)
• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Tuesday, 10 May)

leeoxiang via GitHub

• Re: [webrtc-encoded-transform] Need APIs for using WebCodec with PeerConnection (#121) (Thursday, 12 May)

Lenny via GitHub

• Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Wednesday, 11 May)
• Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Tuesday, 10 May)

Matan Yemini via GitHub

• Re: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63) (Monday, 23 May)

Matt Wolenetz via GitHub

• [webrtc-identity] Enumeration table accessibility issue (#37) (Thursday, 5 May)

Philipp Hancke via GitHub

• Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735) (Monday, 16 May)
• Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108) (Friday, 13 May)
• Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732) (Wednesday, 11 May)
• Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22) (Friday, 6 May)
• Re: [webrtc-stats] transport: add dtlsRole (#629) (Thursday, 5 May)
• Re: [webrtc-stats] transport: add dtlsRole (#629) (Wednesday, 4 May)

Randall Bennett via GitHub

• Closed: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63) (Sunday, 22 May)
• Re: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63) (Sunday, 22 May)

Sergio Garcia Murillo via GitHub

• Re: [webrtc-encoded-transform] Need APIs for using WebCodec with PeerConnection (#121) (Thursday, 12 May)

Varun Singh via GitHub

• Re: [webrtc-stats] outbound-rtp.scaleResolutionDownBy (#620) (Tuesday, 17 May)

Yoav Weiss via GitHub

• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Friday, 20 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• [mediacapture-region] Pull Request: Clarify the cropTarget minting processing model (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Wednesday, 18 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)

youennf via GitHub

• Re: [mediacapture-screen-share] Spec-hooks requested (#213) (Monday, 30 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Monday, 30 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Monday, 30 May)
• Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50) (Friday, 27 May)
• Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51) (Friday, 27 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Tuesday, 24 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Monday, 23 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Monday, 23 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Monday, 23 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 23 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Friday, 20 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 20 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 19 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 19 May)
• [webrtc-encoded-transform] Change generateKeyFrame return value from unsigned long long to unsigned long (#133) (Thursday, 19 May)
• Re: [webrtc-encoded-transform] Make generateKeyFrame take a single RID or none. Resolve the promise with the frame timestamp (#132) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Thursday, 19 May)
• [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48) (Thursday, 19 May)
• Re: [webrtc-encoded-transform] Make generateKeyFrame take a single RID or none. Resolve the promise with the frame timestamp (#132) (Thursday, 19 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Wednesday, 18 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 18 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Wednesday, 18 May)
• Re: [webrtc-pc] The prose around "simulcast envelope" falsely implies that simulcast encodings can never be removed (#2723) (Tuesday, 17 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Tuesday, 17 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Tuesday, 17 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Tuesday, 17 May)
• Re: [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65) (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Monday, 16 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 16 May)
• Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17) (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Monday, 16 May)
• Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 16 May)
• [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46) (Monday, 16 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Friday, 13 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Wednesday, 11 May)
• Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11) (Thursday, 5 May)
• [mediacapture-fromelement] What happens to CanvasCaptureStreamTrack being transferred out of process (#96) (Thursday, 5 May)
• [mediacapture-fromelement] Cloning a CanvasCaptureStreamTrack should return a CanvasCaptureStreamTrack (#95) (Thursday, 5 May)

yuanchao0310 via GitHub

• [webrtc-extensions] senderReceiverTimeOffset should use remoteOutboundRtpStats.roundTripTime (#109) (Thursday, 19 May)

Last message date: Tuesday, 31 May 2022 21:11:15 UTC