Tuesday, 31 May 2022
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [webrtc-pc] insertDTMF is synchronous, but relies on asynchronous state-checking logic (#2738)
- Re: [webrtc-charter] Add link to WebTransport WG in dependencies (#66)
- Re: [webrtc-charter] New specs (#67)
- Re: [mediacapture-region] Unsupported subtypes (#57)
- [mediacapture-region] Pull Request: Unsupported subtypes
- [mediacapture-region] Pull Request: s/throw with a new/throw a new
- [mediacapture-region] Predictable error type for unimplemented Element subtypes (#55)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] Allow cropTo() to fail due to resource limitation (#54)
- [mediacapture-region] Pull Request: Allow cropTo() to fail due to resource limitation
- Re: [mediacapture-region] Revert "Remove obsolete note" (#52)
- Re: [mediacapture-region] Is CropTarget name too generic? (#18)
- Re: [mediacapture-region] Remove obsolete note (name of CropTarget) (#53)
- [mediacapture-region] Pull Request: Remove obsolete note (name of CropTarget)
- [mediacapture-region] new commits pushed by eladalon1983
- [mediacapture-region] Pull Request: Revert "Remove obsolete note"
- [mediacapture-region] new commits pushed by eladalon1983
- Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50)
Monday, 30 May 2022
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- [webrtc-pc] Pull Request: Update to ReSpec version 32.1.7
- [mediacapture-main] Pull Request: Update to latest ReSpec version 32.1.7
Saturday, 28 May 2022
Friday, 27 May 2022
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Clarify the cropTarget minting processing model (#47)
- Re: [mediacapture-region] Clarify the cropTarget minting processing model (#47)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
Thursday, 26 May 2022
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
Tuesday, 24 May 2022
- [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65)
- Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
Monday, 23 May 2022
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] MediaDevices.produceCropTarget -> CropTarget.fromElement (#50)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-screen-share] Introduce DisplayMediaStreamConstraints.dynamicSourceOption (#225)
- Re: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63)
- [mediacapture-main] Pull Request: Improve markup for event tables
- Re: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
Sunday, 22 May 2022
- Closed: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63)
- Re: [mediacapture-output] Controlling 3rd party iframe audio output on a page? (#63)
Saturday, 21 May 2022
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
Friday, 20 May 2022
- [mediacapture-screen-share] Pull Request: troduce DisplayMediaStreamConstraints.dynamicSourceOption
- Re: [mediacapture-screen-share] Dynamic Screenshare Source (Share-this-surface-instead) (#223)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [mediacapture-region] Pull Request: MediaDevices.produceCropTarget -> CropTarget.fromElement
- Re: [mediacapture-region] Is CropTarget name too generic? (#18)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [mediacapture-region] Pull Request: Fix formatting
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-extensions] senderReceiverTimeOffset should use remoteOutboundRtpStats.roundTripTime (#109)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
Thursday, 19 May 2022
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [webrtc-extensions] senderReceiverTimeOffset should use remoteOutboundRtpStats.roundTripTime (#109)
- [webrtc-encoded-transform] Need for modifying metadata (#135)
- [webrtc-encoded-transform] Need to create RTCEncodedVideoFrame from scratch (#134)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- [webrtc-encoded-transform] Change generateKeyFrame return value from unsigned long long to unsigned long (#133)
- Closed: [webrtc-encoded-transform] Should we expose the precise timestamp of the frame that was triggered by a generateKeyFrame call? (#128)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-encoded-transform] Make generateKeyFrame take a single RID or none. Resolve the promise with the frame timestamp (#132)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- [mediacapture-region] Pull Request: Clarify the cropTarget minting processing model
- Re: [webrtc-encoded-transform] Make generateKeyFrame take a single RID or none. Resolve the promise with the frame timestamp (#132)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
Wednesday, 18 May 2022
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [webrtc-pc] insertDTMF is synchronous, but relies on asynchronous state-checking logic (#2738)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- [webrtc-provisional-stats] outbound-rtp.scaleResolutionDownBy (#23)
- Re: [webrtc-stats] outbound-rtp.scaleResolutionDownBy (#620)
- [mediacapture-handle] Pull Request: Fix link to editor drafts
Tuesday, 17 May 2022
- Re: [webrtc-pc] The prose around "simulcast envelope" falsely implies that simulcast encodings can never be removed (#2723)
- Re: [webrtc-pc] The prose around "simulcast envelope" falsely implies that simulcast encodings can never be removed (#2723)
- Re: [webrtc-pc] The prose around "simulcast envelope" falsely implies that simulcast encodings can never be removed (#2723)
- Re: [webrtc-pc] webrtc-pc specifies using '~' in a=simulcast, but does not support RFC 7728 (RTP pause), which is a prerequisite (#2735)
- Re: [webrtc-stats] outbound-rtp.scaleResolutionDownBy (#620)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-extensions] Add a CSP check to RTCPeerConnection.addIceCandidate(). (#81)
- Re: [webrtc-pc] webrtc-pc specifies using '~' in a=simulcast, but does not support RFC 7728 (RTP pause), which is a prerequisite (#2735)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
- Re: [webrtc-pc] webrtc-pc specifies using '~' in a=simulcast, but does not support RFC 7728 (RTP pause), which is a prerequisite (#2735)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
Monday, 16 May 2022
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- Re: [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65)
- [webrtc-pc] Modifications to [[SendEncodings]] from setParameters and sRD can be racy (#2737)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- [webrtc-pc] webrtc-pc does not say to clear RTCRtpCodingParameters.rid when sRD rejects simulcast (#2736)
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65)
- [mediacapture-handle] .sendCaptureAction() seems misplaced on the track (#65)
- Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
- Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- [mediacapture-screen-share] Pull Request: Add spec-hooks for "actively screen-capturing"
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- [mediacapture-handle] Pull Request: Set up Identity spec for automated updates on w3.org/TR/
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)
- [mediacapture-main] Pull Request: Moving Navigator.getUserMedia to a legacy section
- [mediacapture-main] Legacy GetUserMedia extension is not clearly marked "informative" (#882)
Sunday, 15 May 2022
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Should cropTo be able to directly take an element as input? (#19)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
Saturday, 14 May 2022
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
Friday, 13 May 2022
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-handle] Specify 1024 16-bit characters limitation in setCaptureHandleConfig (#33)
- Re: [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- [webrtc-pc] webrtc-pc does not specify what level of support is required for RFC 7728 (RTP pause) (#2735)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
- [webrtc-extensions] RTCRtpEncodingParameters.maxFramerate and other extensions "mature"? (#108)
Thursday, 12 May 2022
- Re: [webrtc-encoded-transform] Need APIs for using WebCodec with PeerConnection (#121)
- Re: [mediacapture-handle] Add README file for Capture Handle Identity (#62)
- [mediacapture-handle] Pull Request: Add wpt tests badges to README.md
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-handle] Add README file for Capture Handle Identity (#62)
- Re: [mediacapture-handle] Add README file for Capture Handle Identity (#62)
- [mediacapture-handle] Pull Request: Add README file for Capture Handle Identity
- Re: [webrtc-encoded-transform] Need APIs for using WebCodec with PeerConnection (#121)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-encoded-transform] Need APIs for using WebCodec with PeerConnection (#121)
Wednesday, 11 May 2022
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [webrtc-extensions] maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders (#107)
- Re: [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730)
- [webrtc-pc] addTransceiver does not check for missing rid properties (#2734)
- [webrtc-pc] addTransceiver does not check for uniqueness of rid (#2733)
- Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
- Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
- Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
Tuesday, 10 May 2022
- Re: [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [webrtc-pc] Inconsistent rules for rid in RTCRtpEncodingParameters (#2732)
- Re: [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223)
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-screen-share] Spec-hooks requested (#213)
- Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223)
Monday, 9 May 2022
- Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223)
- Re: [mediacapture-screen-share] Allow applications to opt-out of source-change (#223)
- Re: [mediacapture-handle] Add CaptureHandleChangeEvent removal in Changelog (#60)
- Re: [mediacapture-handle] Specify event handling with algorithms (#56)
- Re: [mediacapture-handle] Add CaptureHandleChangeEvent removal in Changelog (#60)
- [webrtc-pc] Pull Request: Update to ReSpec version 32.1.6
- [mediacapture-main] Pull Request: Update to latest ReSpec version 32.1.6
Sunday, 8 May 2022
Friday, 6 May 2022
- [webrtc-pc] Inconsistent initialization of scaleResolutionDownBy (#2730)
- [webrtc-pc] Improve WPT testing of setParameters (#2729)
- Closed: [mediacapture-handle] CaptureHandleChangeEvent.captureHandle() when navigating (#53)
- Re: [mediacapture-handle] CaptureHandleChangeEvent.captureHandle() when navigating (#53)
- Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55)
- Re: [mediacapture-handle] Add CaptureHandleChangeEvent removal in Changelog (#60)
- Closed: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Closed: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- Re: [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- [mediacapture-handle] Pull Request: Fix repo metadata in identity spec
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [mediacapture-handle] Pull Request: Add CaptureHandleChangeEvent removal in Changelog
Thursday, 5 May 2022
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- [webrtc-identity] Enumeration table accessibility issue (#37)
- Closed: [mediacapture-screen-share] Avoid user-confusion by not offering undesired audio sources (#219)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)
- Re: [mediacapture-handle] Drop captureHandle() from the event (#57)
- [mediacapture-fromelement] What happens to CanvasCaptureStreamTrack being transferred out of process (#96)
- [mediacapture-fromelement] Cloning a CanvasCaptureStreamTrack should return a CanvasCaptureStreamTrack (#95)
- Re: [mediacapture-main] Add source specific handling for creation and cloning of tracks (#873)
- Re: [mediacapture-main] Add source specific handling for creation and cloning of tracks (#873)
- Re: [mediacapture-main] Add source specific handling for creation and cloning of tracks (#873)
- Re: [webrtc-pc] Document substantive changes since Rec as candidate amendments (#2713)
- Re: [webrtc-pc] Document substantive changes since Rec as candidate amendments (#2713)
- Re: [mediacapture-screen-share] Provide a means to select only part of a screen to capture (#105)
- [webrtc-provisional-stats] Add send bandwidth limitation to stats (#22)
- [mediacapture-region] Pull Request: Remove crop ID leftovers
- Re: [webrtc-stats] transport: add dtlsRole (#629)
Wednesday, 4 May 2022
Tuesday, 3 May 2022
- [mediacapture-handle] Pull Request: Replace usage of "responsible document"
- [mediacapture-handle] Pull Request: A Status of This Document must include at least one custom paragraph.
- [mediacapture-main] Pull Request: Reference relevant global object directly.
- [mediacapture-handle] Pull Request: Drop captureHandle() from the event
- Re: [mediacapture-handle] Specify event handling with algorithms (#56)
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- Re: [mediacapture-handle] Specify event handling with algorithms (#56)
- Re: [webrtc-stats] Remove transport.rtcpTransportStatsId (#625)
- Re: [webrtc-stats] Remove transport.rtcpTransportStatsId (#625)
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
Monday, 2 May 2022
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- [mediacapture-handle] Specify event handling with algorithms (#56)
- Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55)
- Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55)
- Re: [mediacapture-handle] Fix event.captureHandle() when not observable (#55)
- [mediacapture-handle] Pull Request: Fix event.captureHandle() when not observable
- [mediacapture-handle] Pull Request: Fix event
- [mediacapture-handle] CaptureHandleChangeEvent.captureHandle() when navigating (#53)
- Re: [mediacapture-handle] Specify 1024 16-bit characters limitation in setCaptureHandleConfig (#33)
- Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)
- [webrtc-pc] Pull Request: Clean up definitions
- Re: [webrtc-extensions] Add a CSP check to RTCPeerConnection.addIceCandidate(). (#81)
- [webrtc-pc] Pull Request: Update to ReSpec version 32.1.5
- [mediacapture-main] Pull Request: Update to latest ReSpec version 32.1.5