Closed
Bug 1266243
Opened 10 years ago
Closed 5 years ago
Consider removing "Back" button from overflow menu
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: antlam, Unassigned)
References
Details
Attachments
(1 file)
|
510.43 KB,
image/png
|
Details |
Most (if not all) Android devices come with an easily reachable "back" button. Do we really need one in our menu?
Removing it from our menu will give us more room in our menu, simplify the menu, and make it easier for ourselves when we want to add more items to the menu (like bug 1140048).
Looking for any sort of telemetry that might help inform our decision here either way.
| Reporter | ||
Comment 1•10 years ago
|
||
Here's a mock of what it could look like :)
Comment 2•10 years ago
|
||
(In reply to Anthony Lam (:antlam) from comment #0)
> Looking for any sort of telemetry that might help inform our decision here
> either way.
There is an action.1,menu,back event you can look at for back presses from the menu.
However, I don't see a probe for the system back button, so it would be hard to compare.
| Reporter | ||
Comment 3•10 years ago
|
||
(In reply to :Margaret Leibovic from comment #2)
> (In reply to Anthony Lam (:antlam) from comment #0)
>
> > Looking for any sort of telemetry that might help inform our decision here
> > either way.
>
> There is an action.1,menu,back event you can look at for back presses from
> the menu.
>
> However, I don't see a probe for the system back button, so it would be hard
> to compare.
Yeah, I didn't think we measured the hardware back button. :)
Although...just thinking out loud here ...
But given that any content on the web must first be navigated "Back" once before a "Forward" can be performed, shouldn't there be a disproportionate amount of "Back" actions comparatively? So if our telemetry doesn't reflect this relationship, we could assume a lot of users are just using the hardware back button.
If we further couple this with the studies around designing for thumbs [1], we can see that our menu position (which is the pre-req for getting to our "Back" button in the first place) is not only an extra press, but also quite out of the way.
From some brief observations around the office, I've also noticed that most users naturally reach for the omnipresent hardware back over our menu back.
[1] http://www.lukew.com/ff/entry.asp?1927
Comment 4•10 years ago
|
||
It's worth noting that some devices, like the LG G series, use the back button for split screen and thus we'd be depriving those uses access to back history.
| Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Paul [pwd] from comment #4)
> It's worth noting that some devices, like the LG G series, use the back
> button for split screen and thus we'd be depriving those uses access to back
> history.
Sorry, I'm not too familiar with LG. But IIRC these phones do still have "back" buttons. IF not, how else do they return to the last view or exit/undo actions? We could leverage the same button.
Worst case scenario is we can still show it in the menu for these phones.
Comment 6•10 years ago
|
||
(In reply to Anthony Lam (:antlam) from comment #5)
> Worst case scenario is we can still show it in the menu for these phones.
Be careful here, this assumes we have a robust way to determine whether or not this button is present. In our experience, hardware-specific logic can cause headaches.
I'd be interested to know what Chrome does for these devices, since Chrome doesn't have a back button in the menu.
Updated•9 years ago
|
Priority: P1 → P2
Comment 8•5 years ago
|
||
If FF 79 for Android, I see the back button now gone in the menu.
I miss it very much, because on my tablet the hardware back button is hard to find when it's dark.
(Also, it's now less easy to directly go back to an earlier point in browsing history.)
Comment 9•5 years ago
|
||
(In reply to Robert Pollak from comment #8)
If FF 79 for Android, I see the back button now gone in the menu.
I miss it very much, because on my tablet the hardware back button is hard to find when it's dark.
(Also, it's now less easy to directly go back to an earlier point in browsing history.)
It's back in Firefox 80: https://www.mozilla.org/en-US/firefox/android/80.0/releasenotes/
Comment 10•5 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•