← back to v141 · permissions-policy-for-device-attributes-api
conformance · v141
v141 · permissions-policy-for-device-attributes-api — 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-policy-interface |
document.permissionsPolicy (or featurePolicy fallback) is exposed for introspecting device-attributes policy state. | script | … | |
allowsfeature-callable |
permissionsPolicy.allowsFeature is a function callable with the 'device-attributes' feature name. | script | … | |
iframe-allow-attribute |
HTMLIFrameElement.allow reflects, which is how the device-attributes policy is delegated to subframes. | script | … | |
navigator-managed-property |
navigator.managed is exposed in managed-Chrome contexts; this is the API surface the policy gates. | script | … | |
permissions-policy-header-via-meta |
HTMLMetaElement.httpEquiv reflects, the inline carrier for Permissions-Policy directives. | script | … | |
isolated-context-detection |
crossOriginIsolated and isSecureContext exist; this feature targets policy-installed IWAs which require both. | script | … |