We have implemented this on Chrome OS too. On Saturday, April 4, 2020 at 4:23:52 AM UTC+2 Amanda Baker wrote:
> Contact emails > > [email protected],[email protected] > > > > Explainer > > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/TitleBarCustomization/explainer.md > > > > Design docs/spec > > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/TitleBarCustomization/explainer.md > > > > TAG review > > https://github.com/w3ctag/design-reviews/issues/481 > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fdesign-reviews%2Fissues%2F481&data=04%7C01%7CAmanda.Baker%40microsoft.com%7C84c5e8a01bc1471e348f08d7c6b940f0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637196371372837291%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=Jj%2Bb3yKuOMIQrMUJr%2BaLorLv2Jim%2BgNXbphWLoOHcfw%3D&reserved=0> > > > > Summary > > When the window controls overlay 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 the window control buttons > (close, maximize/restore, minimize) are overlaid on top of the client area. > The web app developer is responsible for drawing and input-handling for the > entire window except for the window controls overlay. > > > > Motivation > > Developers want to customize the title bar area so their PWAs feel more > like native apps. > > > > Risks > > Interoperability and Compatibility > > Given that Edge has interest in the feature, there would be at least one > other browser that implements it. The feature involves additive changes > (new web app manifest entry, new JS API, new CSS env variables) and > modifications (changes to frame, new use of env(safe-area-inset-*), but no > removals, so the compatibility risk is minimal. > > > > *Firefox*: No public signals > > *Edge*: Public support (https://github.com/w3c/manifest/issues/847 > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fmanifest%2Fissues%2F847&data=04%7C01%7CAmanda.Baker%40microsoft.com%7C84c5e8a01bc1471e348f08d7c6b940f0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637196371372837291%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=zBrCRyj4csI1dvJR2yvaUu7yppE0f6p%2B53BmjuV8ilM%3D&reserved=0> > ) > > *Safari*: No public signals > > *Web developers*: No signals > > > > 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 in which the app should be launched, so > adding one extra manifest check on startup should have minimal impact. > > > > Activation > > The activation risk is low since this feature includes all the tools > needed to create an app that uses the full extent of the window: new > UA-provided window controls overlay, JS APIs to query the size of the > overlay, and CSS environment variables to layout content around the overlay. > > > > Security > > The major risk is that giving sites partial control of the top of the app > window is it allows developers to spoof content in what was previously a > trusted, UA-controlled region. To minimize the risk of spoofing, the > UA-provided window controls overlay will still display the origin of the > website on startup (this is the current behavior of PWAs). > > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > No > > All platforms will be supported except Android and iOS. These two > platforms already support “fullscreen” display mode and don't use window > controls negating the need for an overlay. > > 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 > > > > Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/feature/5741247866077184 > > > -- 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/9c3197ac-a934-4987-b21f-fda86291b8d1n%40chromium.org.
