← back to v148 · webrtc-datachannel-always-negotiate-data-channels
conformance · v148
v148 · webrtc-datachannel-always-negotiate-data-channels — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
rtcpeerconnection-exists |
RTCPeerConnection is the WebRTC entry point. | exists | … | |
rtcdatachannel-exists |
RTCDataChannel is exposed. | exists | … | |
create-data-channel-method |
RTCPeerConnection.prototype.createDataChannel is a function. | script | … | |
data-channel-priority-property |
RTCDataChannel instances expose a priority property. spec ↗ | script | … | |
data-channel-priority-default-low |
Default priority is 'low' per spec. | script | … | |
data-channel-options-priority-accepted |
createDataChannel({priority:'high'}) is accepted. | script | … |