Revision de23472d66fb6b1bff6b56586c5299c543bd71f5 authored by Emilio Cobos Álvarez on 11 April 2018, 12:15:02 UTC, committed by Emilio Cobos Álvarez on 13 April 2018, 20:20:17 UTC
This tests the resolution in https://github.com/w3c/csswg-drafts/issues/2149.
1 parent cb845c5
RTCRtpSender-getCapabilities.html
<!doctype html>
<meta charset=utf-8>
<title>RTCRtpSender.getCapabilities</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="dictionary-helper.js"></script>
<script src="RTCRtpCapabilities-helper.js"></script>
<script>
'use strict';
// Test is based on the following editor draft:
// https://w3c.github.io/webrtc-pc/archives/20170605/webrtc.html
// The following helper functions are called from RTCRtpCapabilities-helper.js:
// validateRtpCapabilities
/*
5.2. RTCRtpSender Interface
interface RTCRtpSender {
...
static RTCRtpCapabilities getCapabilities(DOMString kind);
};
getCapabilities
The getCapabilities() method returns the most optimist view on the capabilities
of the system for sending media of the given kind. It does not reserve any
resources, ports, or other state but is meant to provide a way to discover
the types of capabilities of the browser including which codecs may be supported.
*/
test(() => {
const capabilities = RTCRtpSender.getCapabilities('audio');
validateRtpCapabilities(capabilities);
}, `RTCRtpSender.getCapabilities('audio') should return RTCRtpCapabilities dictionary`);
test(() => {
const capabilities = RTCRtpSender.getCapabilities('video');
validateRtpCapabilities(capabilities);
}, `RTCRtpSender.getCapabilities('video') should return RTCRtpCapabilities dictionary`);
</script>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...