← back to v155 · stricter-enterprise-policy-enforcement-for-chrome-debugger-api
conformance · v155
v155 · stricter-enterprise-policy-enforcement-for-chrome-debugger-api — 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 |
|---|---|---|---|---|
debugger-api-not-exposed-to-pages |
chrome.debugger is an extension API and is never exposed to web-page script — the process boundary the attach-time policy gate sits on. spec ↗ | script | … | |
attach-rejects-blocked-hosts |
On a managed Chrome 155+ browser where ExtensionSettings configures runtime_blocked_hosts for the extension, chrome.debugger.attach() rejects every target with the error "Host access is restricted by policy." — even targets listed in runtime_allowed_hosts. spec ↗ | manual | … | |
attach-rejects-screenshot-policy |
When DisableScreenshots or a Data Loss Prevention rule restricts capture for the target, chrome.debugger.attach() rejects with "Screenshot capture is restricted by policy." at attach time. spec ↗ | manual | … | |
enforcement-is-all-or-nothing |
The Chrome 155 enforcement is all-or-nothing: any configured runtime_blocked_hosts entry blocks attach() for all targets, deterministically at attach time, instead of individual CDP commands failing unpredictably mid-session. spec ↗ | manual | … | |
no-page-side-attachment-signal |
Attachment is disclosed through trusted browser UI (the debugging infobar); no page-context property, event, or flag (including navigator.webdriver, which reflects WebDriver automation only) reveals a chrome.debugger attachment to the page. spec ↗ | script | … |