Content - d4544ffeccdfe7fdac789a11700fc65d2c65b9cc - 72881f7/webrtc/RTCRtpSender-getCapabilities.html

visit type:

Tip revision: ab86a314a1d287663396aed4a4249d1ad00773db authored by Jinho Bang on 06 April 2018, 12:23:32 UTC
WebNFC: Use [SecureContext] instead of manual check

Tip revision: ab86a31

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>

Browse the archive

https://github.com/web-platform-tests/wpt