Controlled Frame API (available only to IWAs)

Category: Isolated Web Apps-specific API
Type: New or changed feature
Status: In developer trial (Behind a flag) (Chrome 140)
Intent stage: Start prototyping

Summary

Adds a Controlled Frame API available only to Isolated Web Apps (IWAs). This work adds a new Controlled Frame API which is only available to Isolated Web Apps (IWAs). Like similarly-named APIs on other platforms, Controlled Frame allows embedding all content, even third party content that can't be embedded in <iframe>. Controlled Frame also allows controlling embedded content with a collection of API methods and events. For more info on Isolated Web Apps, see the IWA explainer: https://github.com/WICG/isolated-web-apps/blob/main/README.md

Motivation

IWA use cases such as displaying 3p media sites in virtual desktops with minimal latency, common patterns to deploying kiosk applications, and other scenarios all require the ability to embed and manipulate arbitrary web content.

Standards & signals

Specification: https://wicg.github.io/controlled-frame
Firefox: No signal
Safari: No signal
Web developers: No signals
Tracking bug: https://crbug.com/40191772

Samples: https://github.com/WICG/controlled-frame/tree/main/test_app

Explainers: https://github.com/WICG/controlled-frame/blob/main/README.md

View on chromestatus.com