> Actually, if you are in a pinned site and hit a link, a new browser windows is created for the new page but the old one continues living immediately on the left (in the app-manager order). You can retrive it with an edge-swipe from the left border to right. Then, you have browser's back and forward buttons to navigate browser's history.
1. Swiping is an optional feature. If it's not, why is there an option to disable it? 2. Edge gestures have zero discoverability, nobody knows they exist, unless you want show them the FTU videos every 24 hours or so. 3. My devices does not have usable edges. It's extremely uncomfortable to try to swipe from an edge that has only 2mm or so of bezel. 4. My case makes it impossible to swipe from the edge anyway. > Of course, Android users expect a back button, but this doesn't mean it's really a necessity. For example, iOS and Ubuntu Touch don't have one (as far as I know). > > What is a necessity, I think, is being able to perform the following actions: > - Go back to where you were before (in history) > - Go back to the app you were before (in app manager) > - Go back to the view/panel logically precedent the one you are into (in the same app) > - Undo something you did by mistake (and possibly redi it as well) > > Android's back arrow cannot perform all of these at the same time and may have inconsistent behaviour at times. Indeed, I have heard many complaying about it. I don't see how Android's back button *doesn't* do all of these at the same time. All of those can be summarized into "go back one single step, no matter what the action was." This is *exactly* what Android's back button does. It's more like a 'ctrl-z' button, simply undoing your last action. The only people I've ever heard complaining about Android's back button are iOS users, which is so far in the minority considering global smartphone OS usage that it's an opinion that should have far less weight than it actually does. The reality is that when 90% of smartphone users expect a back button on their smartphones, they're going to be sorely disappointed when they try Firefox OS for the first time. And I know it's true, I see it every single time I show someone. On Thu, Nov 26, 2015 at 4:36 PM, Enrico Ghiorzi <[email protected]> wrote: > Il giorno giovedì 26 novembre 2015 16:19:07 UTC+1, Adam Farden ha scritto: > > I can live without widgets on FxOS, I can live with various slowdowns of > the system, but I simply find it infuriating that there is no global back > button. Why Why Why Why Why should I need to go back to the home screen > just to go back to the previous screen? > > > > Every. Single. Android user who had tried my Firefox OS phones has made > the same comment. There's little chance of winning a significant number of > Android users if something so fundemental is missing, and there's even less > chance of getting AOSP or CyanogenMod Devs interested. > > > > Every time I'm in a pinned webapp and I hit a link to an external page I > have to go through this unnecessary circle. > > Actually, if you are in a pinned site and hit a link, a new browser > windows is created for the new page but the old one continues living > immediately on the left (in the app-manager order). You can retrive it with > an edge-swipe from the left border to right. Then, you have browser's back > and forward buttons to navigate browser's history. > > Of course, Android users expect a back button, but this doesn't mean it's > really a necessity. For example, iOS and Ubuntu Touch don't have one (as > far as I know). > > What is a necessity, I think, is being able to perform the following > actions: > - Go back to where you were before (in history) > - Go back to the app you were before (in app manager) > - Go back to the view/panel logically precedent the one you are into (in > the same app) > - Undo something you did by mistake (and possibly redi it as well) > > Android's back arrow cannot perform all of these at the same time and may > have inconsistent behaviour at times. Indeed, I have heard many complaying > about it. > > The more I think about it, the more I believe Firefox OS hasn't yet really > faced this issue in a structural way, but at the same time I'm not sure > Android gets it right as well. > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
