dontcallmedom-bot

Results 99 comments of dontcallmedom-bot

Don't let offers to receive simulcast overwrite existing [[SendEncodings]]

This issue was mentioned in [WEBRTCWG-2023-01-17 (Page 14)](https://lists.w3.org/Archives/Public/www-archive/2023Jan/att-0003/WEBRTCWG-2023-01-17.pdf#page=14)

Handling of contradictory hints

This issue had an associated resolution in [WebRTC December 12 2023 meeting – 12 December 2023 (Issue #276: Handling of contradictory hints)](https://www.w3.org/2023/12/12-webrtc-minutes.html#t02): > RESOLUTION: Consensus to specify an interoperable behavior...

Review mute/unmute/ended and constraints on tracks from getDisplayMedia()

This issue had an associated resolution in [WebRTC March 26 2024 meeting – 26 March 2024 (Clarify each source is responsible for specifying mute/unmute/ended and constraints behavior)](https://www.w3.org/2024/03/26-webrtc-minutes.html#t04): > RESOLUTION: close...

Ability to record non-realtime / frame-by-frame

This issue was mentioned in [WEBRTCWG-2024-02-20 (Page 31)](https://lists.w3.org/Archives/Public/www-archive/2024Feb/att-0008/WEBRTCWG-2024-02-20.pdf#page=31)

deprecate isTypeSupported (was: MediaRecorder specification expects to synchronously know the list of supported mime types)

This issue had an associated resolution in [WebRTC February 2024 meeting – 20 February 2024 (Issue #202 Deprecate isTypeSupported)](https://www.w3.org/2024/02/20-webrtc-minutes.html#t12): > RESOLUTION: Make isTypeSupported return a fixed list of answers and...

mimeType ambiguity: "video/webm;codecs=vp8" means?

This issue had an associated resolution in [WebRTC March 26 2024 meeting – 26 March 2024 (mimeType ambiguity: "video/webm;codecs=vp8" means?)](https://www.w3.org/2024/03/26-webrtc-minutes.html#t05): > RESOLUTION: Align spec with Chrome

setCodecPreferences, sendonly codecs and dummy codecs

This issue was mentioned in [WEBRTCWG-2024-02-20 (Page 18)](https://lists.w3.org/Archives/Public/www-archive/2024Feb/att-0008/WEBRTCWG-2024-02-20.pdf#page=18)

No way to observe DataChannel-only transport events in initial negotiation

This issue was discussed in [WebRTC TPAC 2023 meeting – 12 September 2023 (Issue 2899 No way to observe DataChannel-only transport events in initial negotiation)](https://www.w3.org/2023/09/12-webrtc-minutes.html#t10)

WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track receiving mute/unmute

This issue had an associated resolution in [WebRTC March 26 2024 meeting – 26 March 2024 (Clarify each source is responsible for specifying mute/unmute/ended and constraints behavior)](https://www.w3.org/2024/03/26-webrtc-minutes.html#t04): > RESOLUTION: close...

Should media capabilities influence what is exposed in what is exposed in WebRTC offers and answers

This issue had an associated resolution in [WebRTC February 2024 meeting – 20 February 2024 (Should media capabilities influence what is exposed in what is exposed in WebRTC offers and...