v140 · isolated web apps-specific api

Controlled Frame API (available only to IWAs)

Adds a Controlled Frame API available only to Isolated Web Apps (IWAs).

concepts

  1. IWA-only

    Controlled Frame is now restricted to Isolated Web Apps. Kiosk / digital-signage scenarios still work; general web pages can no longer expose the embedded-browser surface.

  2. Kiosk Builder

    Build the kiosk deployment the chromestatus motivation calls out. Configure URL, partition, nav lock, and autoreload; see the generated <controlledframe> declaration with the matching event hooks.

  3. Capability Probe

    Six gates Controlled Frame requires — secure context, COI, IWA scope, constructor, custom element, policy — checked against your current page. Useful for IWA dev tooling triage.

  4. Nav Policy Tester

    Author a kiosk URL whitelist as glob patterns, then dry-run navigation attempts against it. Mirrors the newwindow/beforeunload interception shape Controlled Frame exposes.

  5. Event Router

    Every event Controlled Frame can route — navigation, permission, dialog, download, find — laid out as a panel of counters with one-click simulations. Shows the host page's interception code.

why it shipped

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.

references