Controlled Frame API (available only to IWAs)

[chasephillips]

Introduction

This proposal introduces a new API to embed arbitrary first and third party content, and to allow the embedder to control that embedded content. The proposed API will only be available to Isolated Web Apps (IWAs).

Through this new API, IWAs can support additional use cases such as latency-sensitive rendering of content overlaid onto a remote virtual desktop session, kiosk installations in public spaces, and managed browsing sessions in educational environments. An API which serves use cases like these is something we have seen in web-adjacent platforms like Electron and believe there is value in standardizing how features like this works.

Read the complete Explainer.

Feedback

I welcome feedback in this thread, but encourage you to file bugs against the Explainer.

Controlled Frame explainer

[cwilso]

As per WICG/controlled-frame#2 and WICG/controlled-frame#3, I think this has enough multiparty support to move into WICG.