Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693)

> Would it be extensible to allow for checking of a share button?

It could, but we would start with the obviously-needed property (back button) and go from there.

Most browsers don't have a very prominent share button, so it's generally acceptable to show one within the page. It doesn't really trigger the "silly double back button" syndrome that an in-page back button does.

> Or do you imply that a back button always means a full browser navbar is available, including share? 

You shouldn't assume this. A solid counter-example would be Android, which would have a back button but no other nav bar.

> A bit unrelated, but would it also be possible to check navigation-control position or orientation? (top, bottom, etc). Example is a non-fullscreen PWA with nav docked to bottom yet the browser has its navbar also in the bottom. This can lead to serious usability issues, and is a fairly common issue on iOS, not sure about Android.

I'd rather not do this. We don't want to expose too much logic about the browser UI to the site, since sites should generally be agnostic as to the browser UI, and we end up baking too much into the spec. That's why I'm carving a very small and explicit space here: just knowing whether there is a back button or not. I don't really want to get into the business of differentiating top, bottom, hardware, software, in-window, system-UI, etc.

-- 
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/693#issuecomment-400910843