demo · v132
Which debug reports actually fire?
Three debug-report kinds — source-debug, trigger-debug, and verbose-debug — each have slightly different gating. Flip the environment toggles to see Chrome 132's new matrix: a partitioned context unlocks verbose-debug even without the legacy ar_debug cookie.
| report kind | fires? | why |
|---|---|---|
| source-debug (registration echo) | — | — |
| trigger-debug (registration echo) | — | — |
| verbose-debug (helper diagnostics) | — | — |
headers that would be sent on a registration
All three report kinds previously required either 3PC + ar_debug cookie, OR the “allow this site to mint debug reports” permission. In 132, partitioned contexts (CHIPS-enabled embedders) auto-qualify for verbose-debug.