← back to v146 · selective-permissions-intervention
conformance · v146
v146 · selective-permissions-intervention — conformance probe
6 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
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
permissions-api-available |
navigator.permissions is the standard surface for querying permission state — the entry point this intervention applies to. | exists | … | |
permissions-query-returns-status |
navigator.permissions.query for a known descriptor returns a PermissionStatus whose state is granted | denied | prompt. | script | … | |
permission-prompt-blocked-without-user-activation |
Sensitive permission prompts (e.g. geolocation) called without user activation are not auto-granted — they resolve to a non-granted state or reject, never silently allow. | script | … | |
permissions-policy-allow-attribute-on-iframe |
iframe elements expose the allow attribute used to grant permissions selectively to embedded documents. | script | … | |
feature-policy-still-reflected |
document.featurePolicy (or document.permissionsPolicy) remains the introspection surface for the active policy. | script | … | |
permissionstatus-onchange-supported |
PermissionStatus exposes onchange so pages can react to intervention-driven revocations. | script | … |