← back to v137 · ip-address-logging-reporting
conformance · v137
v137 · ip-address-logging-reporting — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
no-web-facing-api-for-ip-logging |
IP Address Logging & Reporting is a Chrome Enterprise admin feature with no web-page-observable surface; no navigator.ipAddressLogging or similar global exists. spec ↗ | script | … | |
reporting-api-still-available |
The Reporting API is the closest web platform surface; the ReportingObserver constructor remains available irrespective of enterprise logging. spec ↗ | exists | … | |
navigator-is-object |
navigator is exposed; enterprise logging hooks live below the JS layer and do not pollute it. spec ↗ | typeof | … | |
rtcpeerconnection-still-emits-candidates |
Local/remote IP addresses surface to web content only through WebRTC ICE candidates (gated by mDNS hostname obfuscation); the API is unchanged by enterprise logging. spec ↗ | exists | … | |
fetch-no-extra-headers-from-logging |
fetch() does not gain new IP-address request headers as a result of this feature; the request object remains the standard HTML/Fetch shape. spec ↗ | typeof | … |