← back to v151 · permissions-policy-focus-without-user-activation
conformance · v151
v151 · permissions-policy-focus-without-user-activation — 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 |
|---|---|---|---|---|
iframe-allow-attribute |
HTMLIFrameElement exposes an `allow` attribute — the surface that carries permissions-policy directives like focus-without-user-activation. | script | … | |
focus-method-on-htmlelement |
HTMLElement.prototype.focus exists and is callable; the policy gates programmatic focus calls, so the API surface itself remains in place. | typeof | … | |
window-focus-is-function |
window.focus() is one of the surfaces this policy governs in subframes. | typeof | … | |
showmodal-is-function |
HTMLDialogElement.prototype.showModal is gated by the policy (modal dialogs focus their default button). The method must be present. | script | … | |
autofocus-attribute-reflects |
The autofocus content attribute is one of the surfaces this policy governs; it must reflect on freshly-created inputs. | script | … | |
permissions-policy-known-feature |
If document.permissionsPolicy / featurePolicy is present and exposes features(), 'focus-without-user-activation' should appear as a known feature name. spec ↗ | script | … |