updated feature: Unframed mode (f.k.a. borderless)

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• dt_milestone_desktop_start:
  Old: 116
  New: 146
  


• activation_risks:
  Old:
  New: N/A
  


• all_platforms_descr:
  Old: Implemented on ChromeOS and Linux so far. Enabled by default on ChromeOS only. MobileOS support is not planned.
  New: Implemented on ChromeOS so far.
  


• enterprise_impact:
  Old: 1
  New: 2
  


• shipping_year:
  Old: 2025
  New: 2026
  


• category:
  Old: Miscellaneous
  New: Isolated Web Apps-specific API
  


• doc_links:
  Old: ['https://github.com/WICG/manifest-incubations/blob/gh-pages/borderless-explainer.md']
  New: https://github.com/WICG/manifest-incubations/blob/gh-pages/unframed-explainer.md
  


• enterprise_feature_categories:
  Old: []
  New: 2
  


• ergonomics_risks:
  Old:
  New: N/A
  


• explainer_links:
  Old: ['https://github.com/WICG/manifest-incubations/blob/gh-pages/borderless-explainer.md']
  New: https://github.com/WICG/manifest-incubations/tree/gh-pages/unframed-explainer.md
  


• feature_notes:
  Old: Implementation tracking bug: https://crbug.com/1325830
  New: Umbrella bug b/477025171
  


• interop_compat_risks:
  Old: The feature mostly re-uses the capabilities built with window-controls-overlay (e.g. draggable regions) but additionally it involves new web app manifest entry and changes to frame (hiding the host-native title bar).
  New: The interoperability risk is low for the standard web, as this feature is restricted to Isolated Web Apps (IWAs). The primary risk is that other browser engines may choose not to implement this specific display mode due to long-standing security concerns regarding system UI impersonation (phishing) when an application can hide all host-provided frames. IWAs mitigate these concerns through an enhanced trust and installation model that is not available to standard web origins. Compatibility risk is negligible. "Unframed" is an opt-in value within the display_override manifest field. Browsers that do not recognize the "unframed" value will ignore it and fall back to the next supported display mode in the list (typically "standalone" or "minimal-ui"), ensuring the application remains functional across different environments.
  


• measurement:
  Old:
  New: TODO UseCounters
  


• motivation:
  Old: Developers want to customize the title bar area so their PWAs feel more like native apps.
  New: Standard window decorations, including the title bar and system control buttons, impose fixed UI constraints that restrict available screen real estate and visual integration. Without unframed mode, developers are forced to design around standard operating system frames that often conflict with an application’s specific branding or functional layout requirements. While the Window Controls Overlay API provides a lot of flexibility, it still enforces system-drawn regions for window controls, which prevents a fully bespoke interface. Unframed mode enables Isolated Web Apps to occupy the entire window surface, bridging the gap between web and native application experiences. This level of control is essential for immersive software - such as virtual desktop clients - that requires a unique visual hierarchy or a maximized workspace. By removing standard window borders and title bars, developers can implement unique user experiences with branding that matches the feel of native applications.
  


• name:
  Old: Borderless mode
  New: Unframed mode (f.k.a. borderless)
  


• security_risks:
  Old:
  New: The primary security risk of unframed mode is UI spoofing. By removing the user-agent title bar and window controls, a rogue application could attempt to impersonate operating system UI, browser chrome, or the interface of a different application to perform phishing attacks. This risk is mitigated by restricting the feature to IWAs, and relying on the IWA trust model.
  


• spec_link:
  Old: https://wicg.github.io/manifest-incubations/index.html#dfn-borderless
  New: https://wicg.github.io/manifest-incubations/index.html#dfn-unframed
  


• summary:
  Old: When borderless mode is enabled for installed desktop web apps, the app's client area is extended to cover the entire window - including the title bar area and windowing control buttons (close, maximize/restore, minimize). The web app developer is responsible for drawing and input-handling for the entire window.
  New: Unframed mode extends the Isolated Web App (IWA) client area to encompass the entire window, including the regions normally reserved for the title bar and system window controls. This provides developers with complete control over the application's visual layout, enabling bespoke, immersive experiences and custom window branding. In this mode, the application is responsible for rendering all visual elements and handling user input across the entire window surface.
  

Your next steps:

View feature details

You are receiving this email because:

• You are subscribed to all IWA features

Unsubscribe

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• devtrial_instructions:
  Old: https://github.com/sonkkeli/borderless/tree/main/demo-app
  New: https://github.com/edman/unframed-demo
  


• flag_name:
  Old: enable-desktop-pwas-borderless
  New: enable-unframed-iwa
  


• sample_links:
  Old: ['https://github.com/sonkkeli/borderless/tree/main/demo-app']
  New: https://github.com/edman/unframed-demo
  


• search_tags:
  Old: ['borderless']
  New: unframed, display mode, display override
  

Your next steps:

View feature details

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• measurement:
  Old: TODO UseCounters
  New: UseCounter(WebFeature::kUnframedIwa) https://chromestatus.com/metrics/feature/timeline/popularity/5764
  

Your next steps:

View feature details

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• initial_public_proposal_url:
  Old: None
  New: https://github.com/WICG/manifest-incubations/issues/118
  

Your next steps:

View feature details

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• webview_risks:
  Old:
  New: N/A
  

Your next steps:

View feature details

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• all_platforms_descr:
  Old: Implemented on ChromeOS so far.
  New: This feature is only supported in ChromeOS because IWAs are only available in ChromeOS.
  

Your next steps:

View feature details

[Chromestatus]

Chrome Platform Status

	Updated feature entry:
	Unframed mode (f.k.a. borderless)

Updates made by edm...@google.com:

• interop_compat_risks:
  Old: The interoperability risk is low for the standard web, as this feature is restricted to Isolated Web Apps (IWAs). The primary risk is that other browser engines may choose not to implement this specific display mode due to long-standing security concerns regarding system UI impersonation (phishing) when an application can hide all host-provided frames. IWAs mitigate these concerns through an enhanced trust and installation model that is not available to standard web origins. Compatibility risk is negligible. "Unframed" is an opt-in value within the display_override manifest field. Browsers that do not recognize the "unframed" value will ignore it and fall back to the next supported display mode in the list (typically "standalone" or "minimal-ui"), ensuring the application remains functional across different environments.
  New: The interoperability risk is low for the standard web, as this feature is restricted to Isolated Web Apps (IWAs). The primary risk is that other browser engines may choose not to implement this specific display mode due to long-standing security concerns regarding system UI impersonation (phishing) when an application can hide all host-provided frames. IWAs mitigate these concerns through an enhanced trust and installation model that is not available to standard web origins. Compatibility risk is negligible. "Unframed" is an opt-in value within the display_override manifest field. Browsers that do not recognize the "unframed" value will ignore it and fall back to the next supported display mode in the list (typically "standalone" or "minimal-ui"), ensuring the application remains functional.
  

Your next steps:

View feature details