← back to v140 · controlled-frame-api-available-only-to-iwas
conformance · v140
v140 · controlled-frame-api-available-only-to-iwas — 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 |
|---|---|---|---|---|
controlledframe-not-on-regular-page |
The ControlledFrame interface is intentionally NOT exposed on regular web pages — it is gated to Isolated Web Apps (IWAs). | script | … | |
controlledframe-tag-unknown-element |
Without an IWA context, document.createElement('controlledframe') falls back to HTMLUnknownElement (not a custom interface). | script | … | |
iframe-still-available |
Regular <iframe> remains the embedding primitive on non-IWA pages; the Controlled Frame API is additive. | script | … | |
isolated-app-flag-absent |
On a regular page, window.isolatedApp / crossOriginIsolated alone do not synthesise the Controlled Frame API surface. | script | … | |
no-webview-fallback |
There is no public <webview> custom element on the web platform; Controlled Frame replaces that role specifically for IWAs. | script | … |