Re: [w3c/manifest] Add note on back button requirements (#687)

@tomayac I don't think this PR does anything for the double back button case. Twitter's hack is assuming that wide windows = desktop browser with a back button, and narrow windows = mobile browser without a back button. It's not a strictly correct assumption, but we

a) haven't giving developers better tools to work this out,
b) haven't shipped desktop PWAs on Mac yet
c) and it's a pretty reasonable assumption that users won't access mobile.twitter.com on desktop.

Note that what Twitter are doing here is exactly following the guidance proposed in the PR - try and work out what system UI is present and adjust your UX accordingly. So I'm not sure how adding the guidance is going to prevent the "issue" they have. While the need requirement has been softened, the PR is still essentially telling developers to use UA-detection. :)

Like I mentioned before, we will need a more active mechanism to help with multiple back buttons that's much broader than the fragment proposed here - and that is being fleshed out right now by @mgiuca. So I'm still not convinced we need this particular PR accepted - what we actually want to do is a bigger change to fix the actual problem being discussed - when do developers need their own back buttons.

@jackpalmer1 please don't duplicate post, especially since your comment here isn't relevant to the pull request under consideration. :)

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