W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2022

Re: [webrtc-extensions] Should RtcRtpHeaderExtensionCapabilities offer an "enabled" member? (#99)

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Tue, 22 Feb 2022 12:37:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1047753568-1645533429-sysbot+gh@w3.org>
I think it does -- Chrome just happens to filter "stopped" extensions [here](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/media/base/media_engine.cc;l=62;drc=a2d4701bea545269ad3f5fe6e111adb65c46b8da9) which is not what the spec says.

Does setOfferedHeaderExtensions filter those by default or do we need to modify the algorithm to do so?

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/99#issuecomment-1047753568 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 February 2022 12:37:13 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:56 UTC