- From: Dominick Ng <notifications@github.com>
- Date: Mon, 04 Jun 2018 20:45:40 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 5 June 2018 03:46:03 UTC
Not every app needs a back button, so the _needs_ phrasing in this PR feels quite wrong. More generally, PWAs should function without the crutch of system-level UI at all. If that means they need to include a back button, they should, and if they don't need one, they shouldn't provide one. I think there's a bigger and more complex discussion about _duplicate_ back buttons as mentioned on #673 - when both the platform and app provide one. We could introduce new members to deal with this, and I believe @mgiuca is thinking about that. But this change doesn't do anything for that, and seems to amount to advising developers to use UA-detection for their UI which isn't good. -- 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/pull/687#issuecomment-394572174
Received on Tuesday, 5 June 2018 03:46:03 UTC