v150 · WebRTC

Capability & policy probe

Whether this API works depends on more than the browser version. This page probes navigator.rtc and each method in your current browser, and lays out the full enablement gate: secure context → flag or origin trial → enterprise policy. No fake success — if navigator.rtc is undefined, the probe says so.

Probing…
SurfacePresent?Detail

1 · Secure context

The RTC interface is [SecureContext] — served over HTTPS or localhost. This page: checking…

2 · Flag or origin trial exposes the API

Locally: --enable-blink-features=RTCDiagnosticLogging or chrome://flags/#enable-experimental-web-platform-features. ChromeStatus records an origin trial on desktop, Chrome 150–155 (API, updated 2026-06-25) — but lists no public trial registration as of 2026-07-24 (the trial is enterprise-oriented). The runtime feature RTCDiagnosticLogging — via flag or an origin-trial token — makes navigator.rtc exist.

3 · Enterprise policy authorizes collection

For real diagnostic collection, the managed-browser policy WebRtcDiagnosticLogCollectionAllowedForOrigins must list your origin. Without it, the methods exist but collection is gated by the user agent.

if (!window.isSecureContext) { /* needs HTTPS or localhost */ }

if (navigator.rtc &&
    typeof navigator.rtc.startDiagnosticLogging === "function") {
  // API surface is present — safe to offer diagnostic capture
} else {
  // Not exposed: prompt the user to enable the flag / join the OT,
  // never pretend logging happened.
}

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗