Re: [w3c/manifest] DisplayModeType Borderless (#684)

I by no means have a security background, but if the issue is with apps spoofing security features, then what is the problem with treating the 'borderless' mode as a high-level permission? Provide a maximise/minimise/close api, and if the user gives permission, then the application is trusted to handle it properly.

In that case, 

> ~~What if the operating system doesn't put the 3 buttons on the top-left or top-right?~~

> What if the operating system uses that title-bar space for other business?

The user has explicitly permitted the applications request for that 'business' to be hidden, so it would be reasonable to support. Alternatively, if this platform was stringent about that display, we already have a precedent for how to handle it - fallback to `standalone`. Then the application would be able to respond the same way as if the user denied the borderless permission.

> What if the operating system doesn't have a concept of a title bar at all?

I'd consider mobile OSs not to support the borderless mode - their 'titlebar' is the application switcher that they can close the window with. Again, I dont see an issue with this decision being made by the user agent.

> What if the operating system doesn't give us access to draw into the top bar space at all?

I do think that drawing on top of an existing border is too complex to make generic - The request would be for the chrome/frame/border to be completely hidden, allowing the application full control of the content displayed in its 'area'. 

> What if the user agent wants to add more UI into the title bar in a future version 

With said bar effectively being disabled, users would expect it to be dependent on the app. It could be implemented at the application's discretion

Also, I'd have to be in support of a drag handle API without this feature too - there are quite a few native apps that allow dragging sections other than the titlebar.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/684#issuecomment-529117701