v150 · WebRTC
Capability & policy probe
Whether this API works depends on more than the browser version. This page probes the three static methods on RTCPeerConnection in your current browser, and lays out the full enablement gate: runtime feature → enterprise policy. No fake success — if the statics are undefined it says so, and if the browser still exposes the pre-rewrite navigator.rtc surface it names that as the old API rather than counting it as present.
| Surface | Present? | Detail |
|---|
1 · Runtime feature exposes the API
Locally: --enable-blink-features=RTCDiagnosticLogging or chrome://flags/#enable-experimental-web-platform-features. ChromeStatus (updated 2026-09-30) records status “Proposed”, desktop estimate 156, is_released: false, and no origin trial listed (origintrial: false). Verified in Chrome 154.0.8037.97: the static surface is absent even with the runtime feature on — that flag instead exposes the pre-rewrite navigator.rtc API (start/finish/cancel).
2 · Interface exposure
The current IDL is [Exposed=Window] partial interface RTCPeerConnection — there is no [SecureContext] on it and no Navigator binding. Whether a logging session actually captures anything is implementation-defined and requires user authorisation; the page is never told, so a successful call proves the call, not the capture.
3 · Enterprise policy authorizes collection
For real diagnostic collection on Chromium, the managed-browser policy WebRtcDiagnosticLogCollectionAllowedForOrigins must list your origin. Without it, the methods exist but collection is gated by the user agent.
const S = RTCPeerConnection.startDiagnosticLogging;
if (typeof S === "function") {
// current surface present — safe to offer diagnostic capture
} else if ("rtc" in navigator) {
// pre-rewrite surface only: do NOT call it as if it were the current API
} else {
// Not exposed: prompt the user to enable the runtime feature,
// never pretend logging happened.
}
see also
- Logging lifecycle — start / stop / cancel
- Bug-report companion — metadata limits
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗