updated feature: Controlled Frame API (available only to IWAs)

348 views
Skip to first unread message

Chromestatus

unread,
Feb 27, 2025, 4:21:30 PMFeb 27
to iwa...@chromium.org
Chrome Platform Status
 Updated feature entry:
Controlled Frame API (available only to IWAs)
Updates made by c...@chromium.org:
  • activation_risks:
    Old:
    New: Developers must build an IWA first targeting ChromeOS. The IWA they build must then be deployed in the only available method currently using managed distribution (via policy). These hurdles present significant activation risk. Once the IWA is built, using the Controlled Frame element may require some direct engagement since the methods used to interact with embedded content are complicated. We recommend additional documentation and outreach directly with development partners.

  • api_spec:
    Old: False
    New: True

  • devtrial_instructions:
    Old: None
    New: https://github.com/WICG/controlled-frame/tree/main/test_app

  • interop_compat_risks:
    Old:
    New: This is a new API available only within IWAs. As a new API, it might be subject to the main risk that other browsers may not implement it. However, other browsers must also implement IWAs, and for now we are advancing this to assist our dev partners that are currently using Chrome Apps. The API allows embedding third-party (non-IWA) content. The content will be loaded using the IWA's storage partition so content won't have access to the same site's content as if it was loaded in a tab.

  • privacy_review_status:
    Old: Pending
    New: Issues addressed

  • sample_links:
    Old: []
    New: https://github.com/WICG/controlled-frame/tree/main/test_app

  • security_review_status:
    Old: Pending
    New: Issues addressed

  • wpt_descr:
    Old: Not yet, we plan to add IWA-specific web platform tests as part of our work.
    New: WPT does not support PWA/IWA test environments. Once that support is available, we can investigate adding IWA-focused WPT tests. Until then, we have built a pseudo-WPT test environment so we can write WPT-like tests that work in an IWA context. These are available for review in the Chromium code repository: //chrome/test/data/controlled_frame: https://source.chromium.org/chromium/chromium/src/+/main:chrome/test/data/controlled_frame/ //chrome/browser/controlled_frame/controlled_frame_wpt_browsertest.cc: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/controlled_frame/controlled_frame_wpt_browsertest.cc?q=add_content_scripts&ss=chromium%2Fchromium%2Fsrc

Your next steps:

You are receiving this email because:

  • You are subscribed to all IWA features

Unsubscribe

Chromestatus

unread,
Feb 28, 2025, 4:53:57 PMFeb 28
to iwa...@chromium.org
Chrome Platform Status
Updates made by ajayra...@google.com:
  • shipped_milestone:
    Old: None
    New: 135

Your next steps:

Chromestatus

unread,
Feb 28, 2025, 6:04:17 PMFeb 28
to iwa...@chromium.org
Chrome Platform Status
Updates made by rmce...@chromium.org:
  • summary:
    Old: Adds a Controlled Frame API available only to Isolated Web Apps (IWAs). This work will add 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
    New: 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

Your next steps:

Chromestatus

unread,
Feb 28, 2025, 6:46:58 PMFeb 28
to iwa...@chromium.org
Chrome Platform Status
Updates made by sada...@google.com:
Your next steps:

Chromestatus

unread,
Mar 2, 2025, 6:21:20 PMMar 2
to iwa...@chromium.org
Chrome Platform Status
Updates made by davi...@google.com:
Your next steps:

Chromestatus

unread,
Mar 3, 2025, 3:55:47 AMMar 3
to iwa...@chromium.org
Chrome Platform Status
Updates made by pfa...@google.com:
Your next steps:

Chromestatus

unread,
Mar 4, 2025, 2:47:17 PMMar 4
to iwa...@chromium.org
Chrome Platform Status
Updates made by ajayra...@google.com:
  • shipped_milestone:
    Old: 135
    New: 136

Your next steps:

Chromestatus

unread,
Mar 4, 2025, 2:47:29 PMMar 4
to iwa...@chromium.org
Chrome Platform Status
Updates made by ajayra...@google.com:
  • shipped_milestone:
    Old: 136
    New: 136

Your next steps:

Chromestatus

unread,
Mar 6, 2025, 2:44:07 PMMar 6
to iwa...@chromium.org
Chrome Platform Status
Updates made by c...@chromium.org:
  • activation_risks:
    Old: Developers must build an IWA first targeting ChromeOS. The IWA they build must then be deployed in the only available method currently using managed distribution (via policy). These hurdles present significant activation risk. Once the IWA is built, using the Controlled Frame element may require some direct engagement since the methods used to interact with embedded content are complicated. We recommend additional documentation and outreach directly with development partners.
    New: Developers must build an IWA to use the Controlled Frame API. The IWA they build must then be deployed, currently using managed distribution via enterprise policy. These hurdles present significant activation risk since each of these are new technologies and require interaction with multiple systems. Once the IWA is built, using the Controlled Frame element may require some direct engagement since the methods used to interact with embedded content are complicated. We recommend additional documentation and outreach directly with development partners.

Your next steps:

Chromestatus

unread,
Mar 6, 2025, 7:48:24 PMMar 6
to iwa...@chromium.org
Chrome Platform Status
Updates made by c...@chromium.org:
  • tag_review:
    Old:
    New: https://github.com/w3ctag/design-reviews/issues/1067

Your next steps:

Chromestatus

unread,
Mar 10, 2025, 4:11:08 AMMar 10
to iwa...@chromium.org
Chrome Platform Status
Updates made by tomm...@google.com:
Your next steps:

Chromestatus

unread,
Mar 18, 2025, 8:50:04 PMMar 18
to iwa...@chromium.org
Chrome Platform Status
Updates made by ddwo...@google.com:
Your next steps:

Chromestatus

unread,
Mar 18, 2025, 10:34:41 PMMar 18
to iwa...@chromium.org
Chrome Platform Status
Updates made by dom...@chromium.org:
Your next steps:

Chromestatus

unread,
Mar 28, 2025, 7:57:25 PMMar 28
to iwa...@chromium.org
Chrome Platform Status
Updates made by rmce...@chromium.org:
  • shipped_milestone:
    Old: 136
    New: 138

Your next steps:
Reply all
Reply to author
Forward
0 new messages