- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Mar 2018 16:16:52 +0000
- To: public-webrtc-logs@w3.org
Hi all, @rakuco and I are looking into normative spec changes that don't have tests this quarter, in this [tracking doc](https://docs.google.com/document/d/1kFYTqUMEbo9p87i6wAzORoicMWgHsuYwL2CgtvdhDaE/edit?usp=sharing). This is the last week of the this effort, and I ended up here this week. After looking around for a bit it looks like there is an existing test which could fairly easily be modified to cover this change: https://github.com/w3c/web-platform-tests/blob/172fe9d52634f70dd2810c4a859acd1aa6dc365a/webrtc/RTCRtpParameters-headerExtensions.html#L58 I think the new test would just have to omit the `encrypted` member and then use `getParameters()` to verify it behaves the same as when an explicit false was given. I see "The headerExtensions sequence is populated based on the header extensions that have been negotiated for sending" in the spec so maybe a loopback call needs to be set up to test this, I'm not sure. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1816#issuecomment-377560600 using your GitHub account
Received on Friday, 30 March 2018 16:16:57 UTC