Fenix: Put the navigation buttons in the main UI for "large-enough display" devices

[Pomax]

The new FF for Android removed tabs and navigation buttons for devices large enough to accommodate those (10" tablets, etc), and has made the user experience so horrible that at least personally I had to switch to Chrome. I hate Chrome, but the inability to switch tabs and quick-navigate without having to dive into menus is so frustrating that I can't keep using FF.

https://github.com/mozilla-mobile/fenix/issues/2344 is already open for restoring tabs, but there does not appear to be one for putting the navigational buttons back in the main UI if there is enough screen real-estate to do so, so please consider this a feature request parallel to https://github.com/mozilla-mobile/fenix/issues/2344 to also add the "back"/"forward"/"reload" buttons back into the main UI, with an option added to the custom settings to set "show nav buttons in the main UI: [never] [auto] [always]" or something similar that offers users those three choices.

[s-ankur]

Duplicate of https://github.com/mozilla-mobile/fenix/issues/2344. Please check out that issue

[s-ankur]

It's been added to the UX MVP Project https://github.com/mozilla-mobile/fenix/projects/2#card-21229607 . It means they consider it to be part of the minimum viable product so it has a considerable priority. The team is pretty small so the delay is understandable, at least to me.

If you have some request not covered by the original issue, feel free to comment there or edit this issue to the specific request that you want to make

[Pomax]

Title and comment updated so as to be about the nav buttons, mentioning the already existing issue for tabs

Having said that, the project you're linking to is closed, last updated July 16, so is that issue also a card in a still-active project, or did it fall off the larger roadmap? (because I don't see it listed in anything other than that one closed project according to https://github.com/mozilla-mobile/fenix/issues/2344, which suggests no one's going to ever see it again, rather than it being high priority)

[s-ankur]

Sorry about misleading you, I thought that project was open.

4134 covers your remaining request I think.

[Pomax]

Very strange: I see it subsumed into https://github.com/mozilla-mobile/fenix/issues/4498, and if I load that issue, it says it's in the "Fenix Product Backlog" project. However, when I load up that project board, I don't see that meta issue for tablet optimization in any of the tracks. In fact, searching for 44xx issues within that project only shows issue 4417, which is a very different issue indeed.

It still feels like this has somehow fallen off the roadmap.

[amedyne]

Closing this ticket. Keeping #4498 open to be considered for future Fenix backlog.

[Pomax]

still salty that we had no choice in the matter and we were forced into a phone UI. So until this gets fixed, I'm going to keep using Chrome for a handful of things, and duckduckgo for everything else, as much as I loved Firefox. I'll happily switch back when it works like a normal browser on tablet again (which is the only device I use for media consumption)