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

From a security standpoint, a permission doesn't necessarily make us feel safer. We often see proposals for new permissions that amount to "Do you want to give this application permission to show potentially misleading security UI in the future?" and those prompts are extremely difficult to word in such a way that the user will understand what they are granting, since the benefits and drawbacks are not obvious to someone who doesn't understand the security consequences. Many users will just grant the permission, not seeing any downside, and then at a later time, they may be tricked into thinking they are somewhere that they're not.

Outside of security: I still have great concerns around portability and usability. If we give a web app the ability to draw into the system-supplied title bar, it is basically impossible to make use of that ability without knowing at least something about the host OS, such as whether it draws its caption buttons on the left or right side of the window, and it's impossible to make it look good without knowing something about the style the host OS uses (such as does it have flat buttons or 3D-looking buttons). This will lead sites down a path we try very hard to avoid: detecting the top 1 or 2 host operating systems and integrating well with those, and then ignoring the rest. I guarantee if we allow this, there will be some sites that look good on Windows 10 and trash everywhere else (up to and including drawing over the top of caption buttons), and some other sites that look good on the latest macOS and trash everywhere else. Our mission as web platform designers is to create an abstract interface that allows sites not to care about what the host OS is at all, and let the user agent make all of those decisions on behalf of the site.

-- 
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-531642027