- From: Matt Giuca <notifications@github.com>
- Date: Wed, 13 Jun 2018 23:10:06 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/673/397182282@github.com>
We had a chat about this yesterday (internal to Google) and I've been discussing an internal proposal to do basically two things: 1. Give developers explicit control over whether a back button, and other UI elements, are shown (rather than just leaving it up to the UA and the vague descriptions of "standalone" and "minimal-ui" in the spec), and 2. Give developers a way to query whether the UA is currently showing a back button (either UA-provided, system-provided, or in hardware). The main problem I am trying to solve is this "double back button" as shown here (actual screenshot from the Twitter PWA in the Microsoft Store):  This is due to the app not knowing whether the system is providing a button. I don't *think* we really need to give developers explicit control over whether there's a back button --- certainly we can't give absolute control because the UA can always decide to add a back button, or may be forced to by having a system or hardware one. I think it's quite sufficient to merely *tell* developers whether there is a back button. Thus, I'm going to focus on number 2 for the time being (will file a separate bug). -- 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/673#issuecomment-397182282
Received on Thursday, 14 June 2018 06:10:29 UTC