← back to v150 · webrtc-diagnostic-logging-api
conformance · v150
v150 · webrtc-diagnostic-logging-api — conformance probe
7 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
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
navigator-rtc-binding |
navigator.rtc exists — the RTC interface binds to Navigator inside a secure context with the RTCDiagnosticLogging runtime feature on. spec ↗ | exists | … | |
rtc-start-method |
navigator.rtc.startDiagnosticLogging is a function — begins a session and resolves with the session UUID. spec ↗ | typeof | … | |
rtc-finish-method |
navigator.rtc.finishDiagnosticLogging is a function — finalises the local log file. spec ↗ | typeof | … | |
rtc-cancel-method |
navigator.rtc.cancelDiagnosticLogging is a function — discards the captured data (the spec's IDL name, not the explainer example's cancelLogging). spec ↗ | typeof | … | |
secure-context-gate |
The interface is [SecureContext]: on a non-secure context navigator.rtc must be absent (on a secure context either state is spec-legal, since the runtime feature also gates it). spec ↗ | script | … | |
metadata-entry-limit-rejects |
When bound, startDiagnosticLogging() with 6 metadata entries rejects before any recording starts (spec mandates TypeError; Chromium main currently rejects with RangeError — rtc.cc RejectWithRangeError — so either name proves enforcement). spec ↗ | script | … | |
metadata-length-limit-rejects |
When bound, startDiagnosticLogging() with a metadata value over 100 characters rejects before any recording starts (spec mandates TypeError; Chromium main currently rejects with RangeError, measuring UTF-8 bytes — rtc_logging_utils.h — so either name proves enforcement). spec ↗ | script | … |