Contact emails
[email protected] (preferably google.com), [email protected] Explainer https://github.com/sonkkeli/borderless/blob/main/EXPLAINER.md Specification Not ready yet but on-going here go/borderless-design-doc (googlers-only) TAG review Not yet filed. Blink component N/A, this feature is not large enough to need one. Summary 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. (See go/additional-windowing-controls regarding additional windowing controls.) Motivation Developers want to customize the title bar area so their PWAs feel more like native apps. Risks Interoperability and Compatibility 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 native title bar). Firefox: No public signals Edge: No public signals Safari: No public signals Web developers: Strong positive - partners Ergonomics The changes associated with this feature will only be enabled for PWAs that opt-in to it, so there are minimal risks posed to the browser as a whole. A PWA that opts-in to the feature should also have minimal ergonomics risk since the manifest already needs to be parsed on startup to determine the correct display mode (which then gets enabled when the Window Management permission has been given), so adding one extra manifest check on startup should have minimal impact. Security The major risk is that by giving sites control of the top of the app window, it allows developers to spoof content in what was previously a trusted, UA-controlled region. To minimize the risk of spoofing, to enter borderless mode Window Management permission must be granted and the app’s origin will be shown in the app settings. When navigating out of scope of the web app will bring back the title bar and show a custom tab bar containing the current origin with a close button returning back to the origin. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? No, we are only targeting desktop OSs. Is this feature fully tested by web-platform-tests <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%2F%2B%2Fmaster%2Fdocs%2Ftesting%2Fweb_platform_tests.md&data=04%7C01%7CAmanda.Baker%40microsoft.com%7C84c5e8a01bc1471e348f08d7c6b940f0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637196371372857279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=M79bBRPkECK4YmZwW1JAdcqHCofWo6qpz3TFFwnvqB8%3D&reserved=0> ? No, N/A not implemented. There will be browser tests in web_app_frame_toolbar_browsertest.cc <https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/views/web_apps/frame_toolbar/web_app_frame_toolbar_browsertest.cc> . Feature flag (until launch) chrome://flags#enable-desktop-pwas-borderless Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5551475195904000 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4ad86ea7-a144-4f95-b66f-7d457448143en%40chromium.org.
