- From: jackpalmer1 <notifications@github.com>
- Date: Mon, 04 Jun 2018 20:48:09 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 5 June 2018 03:48:32 UTC
Can there be a standard drawing API for this than? Because we really want custom looking tabs in our app and this restriction is making the flow irregular? At-least for developers that do cross platform testing, a bit of control is necessary. We can always have this, but a bit more control would be beneficial for the UX. > Removing the top bar also makes it impossible to drag the app window to reposition it on the screen on Chrome OS, which seems like a bigger usability problem. Add some margin to the buttons where it will still be drag able. This is an easily fixable problem if we take some minor precautions. > Another problem is that there is no guarantee a to where the OS buttons would end up. For instance, MacOS puts the close buttons on the left, while windows does it on the right... and this could change from one OS version to another... and could be even more inconsistent on mobile, where close buttons are generally not a thing. Its a progressive web app. We as developers take care of the cross platform support, but choice should be given to us to make more creative use of this space. -- 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-394572522
Received on Tuesday, 5 June 2018 03:48:32 UTC