Open Bug 1979656 Opened 1 year ago Updated 12 days ago

New Tab Management UI one-handed ergonomics improvements

Categories

(Firefox for Android :: Tabs, enhancement)

Firefox 143
All
Android
enhancement

Tracking

()

People

(Reporter: lilydjwg, Unassigned)

References

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:143.0) Gecko/20100101 Firefox/143.0

Steps to reproduce:

Try to switch tabs via the tab list on a phone.

Actual results:

With the UI, the tab list occupies the whole screen and my first two tabs along with suspended tabs are out of reach. I have to use another hand to select my tabs, which is very inconvenient (e.g. when commuting on a bus or subway train, my other hand needs to hold to the handrail; moving my holding hand up can make it reachable but isn't always an option because the phone may easily fall off my hand while traveling).

Expected results:

In the past, when the tab list occupied only 3/4 of the screen height and I could reach even the first tab with the hand holding my phone.

Please either make my tabs nearer or make the list scrollable / movable so I can reach them easily.

Hi!
Thanks for reporting this bug! We intentionally moved from a bottom sheet to a full screen fragment here but thank you for the feedback. We will take this into consideration

Severity: -- → N/A
Status: UNCONFIRMED → NEW
Type: defect → enhancement
Component: General → Tabs
Ever confirmed: true

I'm unsure how to add some weight to this bug so I'll just write my thoughts.

The full screen design really leaves those who prefer to interact with their phone on the bottom with a loss of ergonomic functionality. When you are stuck reaching to the top of the screen to do anything with the tabs, especially with a larger phone, you have a really poor experience overall. There are a lot of options to put toolbars on the top, the bottom, use single or double line arrangements, both sticky and slide-away which are appreciated. But there is no option or set of settings that let the user manage tabs from the lower half of the phone screen. Either allowing the tab strip UX to attach to the bottom or pinning tabs to the bottom of the screen (growing up) would be great for users like me and, I'm assuming, the original bug reporter..

Thanks for filing this bug and the conversation! I think this raises a good UX consideration. Maybe we can explore having the tabs populate from the bottom-up when the Toolbar is set to the bottom position.

We'll be discussing this and other components of the redesign soon with our UX and Product partners.

Samsung Internet handles this pretty well: the tab list starts at the top of the screen, but you can drag down to pull the topmost tabs to where your thumb can reach.

Ie, there is about 50 mm of blank space above the tab list. When opening the tab manager the blank space is off the top of the screen. But you can drag down with your thumb to reveal the empty space and bring the tabs down to within thumb reach.

It's a feature of a lot of Samsung apps (Messages etc) it's nice. It makes handling lists one-handed much easier.

(In reply to Nicholas Poon (redirect NI to npoon2003@gmail.com) [:Nick] from comment #1)

We intentionally moved from a bottom sheet to a full screen fragment here

Hello, I don't see any other discussions regarding this particular design choice, so i'd like to direct attention to it specifically. Referencing https://bugzilla.mozilla.org/show_bug.cgi?id=1971400 and https://phabricator.services.mozilla.com/D255850

To me, this is the most crucial regression in the new tabs manager. Where many other mobile applications are only now migrating to a unified sliding dialog UX (where Firefox Fenix was ahead of the curve with it's previous design), this is a major step back.

Could we please provide some details on the design discussions that took place, specifically to replace the drawer with a fullscreen menu? I've combed Phabricator for related discussions and do not have a Figma account to view those links.

I fully appreciate the work being done on the new tabs manager and resolving long-standing bottom-sheet issues, but this top-level paradigm change is rough. I've been trying to restore the old UX code for the last day or two (from https://bugzilla.mozilla.org/show_bug.cgi?id=1975314), but this isn't sustainable.

Over a year in, the new full-screen Tabs Menu is the most sharp and hard-to-grasp regression in the 2026 redesign. It is literally hard to grasp in a physical sense, because my thumb cannot easily reach the top of the screen to interact with the menu header or first tabs.

This is such a crucial issue that I am still daily-driving the old UI/UX on the now-insecure v148.0.2, while monitoring development channels for any discussion on the Android UX. Mozilla employees on Reddit claim this is being discussed and handled, but I do not see any evidence on Bugzilla of work being planned. At the moment, there doesn't seem to be any attention directed at this portion of the UI while Tab Groups are under rapid development.

I want to try and make headway on refining this design. Kindly pinging Noah, Nick, and Cathy from BUG 1971400 where the regression was made.


Maybe we can explore having the tabs populate from the bottom-up when the Toolbar is set to the bottom position. We'll be discussing this and other components of the redesign soon with our UX and Product partners.

Has there been any movement on this discussion? How can I or anyone else get involved? What are our next steps?

It is very frustrating that these far-reaching design choices are made in a bubble behind closed doors and private Figma links, where the greater community cannot validate and audit prospective designs before time is spent on development and implementation.


We intentionally moved from a bottom sheet to a full screen fragment here

This is the core design flaw. I must ask, why was that decision made? The single reason I can think this change would make sense is to make room for the new Tab Groups bottom drawer, which could have reasonably been implemented over the existing drawer.

The usability issue detailed in this bug report is easily resolved by re-implementing a collapsible Bottom Drawer similar to the previous design. I've attached a screenshot to demonstrate (the demo tray also uses a full-screen state once expanded).


Again and with all seriousness, what are our next steps to resolve this regression with one-handed use, and how can I help as a non-Mozilla employee?

Flags: needinfo?(npoon)
Flags: needinfo?(nbond)
Flags: needinfo?(calu)

Thanks again for providing feedback and being passionate about the ways we can make improvements.
I will pass this along to our Product and UX.

Flags: needinfo?(npoon)
Flags: needinfo?(nbond)
Flags: needinfo?(calu)
Summary: New Tab Management UI pushes my tabs far away and hard to reach → New Tab Management UI one-handed ergonomics improvements

Sorry Cathy, I tagged you under the assumption that you were part of the UX team. I appreciate your response, but please understand: I have no confidence that this issue will be resolved via internal meetings that the affected users are not part of.

Respectfully, can a representative from the "Product and UX" team please join the public-facing discussion, and stay engaged with this report?

Otherwise it's a telephone game, where information is relayed between uninterested parties, and key details+urgency are always lost.

I think it would better to allow user to customize initial and limit largest menu height

Thanks to everyone involved in this conversation, and to the original poster as well. Some updates from UX:

@breakingspell I remember our conversation on Mozilla Connect about the one-handed ergonomics and accessibility problems with the new Android designs, and I wanted to follow up here myself rather than have this passed along again.

I also want to acknowledge the bigger change behind a lot of the frustration here = moving the tab tray from a bottom sheet to a full-screen experience. I wasn’t part of that original decision, but I do want to share some context - we’re continuing to add functionality to the tab view that wouldn’t scale well within the old bottom-sheet model. That doesn’t make the ergonomic tradeoffs of the full-screen layout any less real though, and there’s still a lot we can improve including doing a better job of sharing upcoming explorations and changes earlier.

One piece of progress to share is an exploration that moves the tab controls to the bottom of the view, putting them back within easier thumb reach. Here’s a design prototype APK to try. If anyone here is willing to test it, I’d really like to hear what feels better, what still feels difficult, and any other ideas you have for improving the ergonomics.

This APK doesn’t fully address this specific ticket though (the placement of the tabs themselves when only a few are open). The ideas shared here around bringing those tabs closer to the thumb have been really helpful, and we’ll explore improvements there, too.

I’ll also keep the original Mozilla Connect conversation updated as we have meaningful progress to share, so there’s a more accessible place for the broader community to follow along and contribute feedback.

And thank you all for the time and effort you’ve put into documenting these problems and proposing alternatives. We can do a better job of sharing explorations and progress along the way, and I’ll work to make that happen.

Rylee, thanks very much for the response and explanation. I really do appreciate you taking the time here and on Connect to engage with us. Here's hoping we can figure out a UI/UX that everyone is able to use without issue.


Regarding the design change showcased in the test APK: the new menu for private/synced tab controls is another step backwards. A floating pill-shaped menu obstructs the tab list/grid, and provides no additional interactivity or value.

With a drawer implementation, the tab controls comprised the header of the drawer, and provided an interactive grab point for swiping down to close the menu. In the full-screen menu, the tab control elements retained the same "header" appearance but lost interactivity.

Ideally, the tab controls changed in this test would remain "headers", and bottom-align as a "footer" for bottom-toolbar users (driven by the bottom toolbar customization or separately). Not a pill menu, please!


If you could relay these key points to the powers that be, thank you in advance:

  • The tab controls (Private/Groups/Synced) should remain a "header" or "footer" of the tab menu, not a floating pill element drawn over tabs.

    • This header or footer should be interactive, allowing directional swipes to switch tab types and to close the tab menu without a device Back gesture.
    • The "Address Bar Location" customization option should set the tab menu header/footer position.
  • Re-visit a drawer implementation of the Tabs Menu now that new features have shipped.

    • My example video proves this is possible from a technical, functional, and stylistic standpoint. This design scales with new features such as Tab Groups, they fit into the header row along with the others.
    • A drawer is objectively better to present content such as tabs, in any application. The drawer can be "expanded" to become a full-screen menu, then swept down within easy reach of a thumb. A full-screen-only menu requires constant hand movement compared to a drawer driven by a single thumb. Walking back this design choice would resolve most one-handed strain.
    • This drawer should also position elements based on the Address Bar Location setting, or potentially provide a standalone setting.

I just got access to the new tabstrip bottom design in nightly and I wanted to say thank you for what has already been made available. I'm sure there is more work to be done to support things but even in this current state my own usage pattern has been addressed (low tab count, accessible one handed).

As this should also be constructive comment and not just a gushing thank you, I did see some fit and finish items.

  • When playing a vertical video full screen the drag tip toast overlays the tab bar.
  • The tab bar and URL bar don't share a theme and the URL bar has a light border line at the top creating a subtle but "can't unsee it" break in the UX. The lighter border line works when that URL is on it's own but should be moved to be above the URL bar when both are enabled.

158.0.a1 build 2016185887, android 16, Samsung Ultra 24

(In reply to JoshH from comment #15)

I just got access to the new tabstrip bottom design in nightly and I wanted to say thank you for what has already been made available. I'm sure there is more work to be done to support things but even in this current state my own usage pattern has been addressed (low tab count, accessible one handed).

As this should also be constructive comment and not just a gushing thank you, I did see some fit and finish items.

  • When playing a vertical video full screen the drag tip toast overlays the tab bar.
  • The tab bar and URL bar don't share a theme and the URL bar has a light border line at the top creating a subtle but "can't unsee it" break in the UX. The lighter border line works when that URL is on it's own but should be moved to be above the URL bar when both are enabled.

158.0.a1 build 2016185887, android 16, Samsung Ultra 24

Thank you for the feedback!
Regarding the two issues reported:

When playing a vertical video full screen the drag tip toast overlays the tab bar.

Can you open a new ticket and attach a video recording of the issue?

The tab bar and URL bar don't share a theme and the URL bar has a light border line at the top creating a subtle but "can't unsee it" break in the UX.

Nice catch! Yes, I agree this should be fixed.

Flags: needinfo?(josh)

Hey Rylee, could you address the light border line that is in between the bottom tab strip and the url address bar this user is pointing out?

Flags: needinfo?(ryfrazier)

Sure thing! There shouldn't be a divider line between the bars. Thanks so much for catching this JoshH! Appreciate the help with maintaining high quality 🙌

Flags: needinfo?(ryfrazier)
See Also: → 2074898

Hello all,

Has there been any movement on the UX team's internal discussions regarding the Tab Menu/Drawer, based on feedback from this thread and Mozilla Connect?

If it hasn't already taken place in a meeting or call, this video and these points supporting a drawer menu style should be directly presented to those that make design decisions. I'd like to know their reactions: if they considered it, if they dismissed it out of hand, or if they had constructive points for refinement.

Rylee, I apologize for tagging you only to ask for help relaying discussions to another team, but could you assist us again in contacting the UX team?
Above all else, if someone from the UX team could directly join the discussion here, we can get productive and refine this design much more effectively.

Formally, could we request time from a representative in the Android UX team to join us here on this Bugzilla thread? Specifically someone with firsthand knowledge of the internal discussions that resulted in the current design, and with the ability to provide and receive actionable feedback.

Flags: needinfo?(ryfrazier)

(In reply to breakingspell from comment #14)
Super great feedback here! You'll soon start to see the floating toolbar version in tab tray in Nightly, as we continue our tests, but your early feedback is helping to shape what all to consider including. Options for settings (and having it map to address bar setting) and swipe gestures are key things standing out here - you won't see this in the upcoming Nightly version, but it is impacting iterations outside of that test, so thank you so much.

Heads up, we've also got more we're looking to bring to tabs experience - I plan to share more about this in the original Moz connect thread soon. Will look forward to your thoughts!

Flags: needinfo?(ryfrazier)

I plan to share more about this in the original Moz connect thread soon

Rylee, kindly ensure the primary Connect Idea thread regarding these UX changes is given focus, not the smaller thread we first interacted in.


you won't see this in the upcoming Nightly version, but it is impacting iterations outside of that test

I can build from source and do not have to wait for Nightly channel, do you have these patches/differentials or links to these iterations? I scoured Bugzilla and cannot find any evidence or code for customization or swipe gestures in the Tab Menu.


If I can express frustration over this ongoing disconnect with design traditions: A radical new element (floating pill toolbar) was prioritized over the longstanding accessibility regressions caused by the new menu. A floating toolbar will make thumb strain even worse: when the menu is full-screened with tabs populating from the top, moving the header to a toolbar further pushes those tabs up out of reach.

Please, can we answer why a drawer presentation is not being reconsidered? Bringing all tab elements within thumb reach (as it had done for years) would resolve this one-handed accessibility case in one fell swoop.

I must press again for a knowledgeable representative from the UX Team to join us. We cannot make meaningful progress if they don't even understand the core a11y issue!

Flags: needinfo?(ryfrazier)

(In reply to breakingspell from comment #21)
Hi @breakingspell,

I feel I may have caused some confusion, so here to clear things up.

I’m on the UX team. I’m a designer on Firefox for Android, directly on the tab tray work, and I’m staying on this thread. I had just joined when we first talked on Connect and wasn’t part of the original bottom sheet → full view decision, but I care after this experience now.

My understanding of the a11y issues: The full-page tray put both the controls and the tabs at the top of the screen. With only a few tabs open, the tab you need sits at the farthest point from your thumb, so one-handed users, including people with one hand or limited reach, have to regrip or set the phone down every time. Swipe-to-dismiss went away with it. Muscle memory was broken, and those posts were hard to read. We’ve shipped some smaller reachability refinements so far (tab size, empty space, active tab placement), but there’s more to do, and we need to communicate changes earlier.

“Iterations” meant design explorations, not code. There are no patches. Sorry I wasn’t clearer; I know you spent time looking.

The drawer is not being reconsidered because the tray is becoming a management surface. Search and tab groups (with drag and drop) are in; pinned tabs, filters, tab resizing (button and gesture), and smart supports for people who opt into AI features are next in explorations. A bottom sheet owns the vertical drag for itself, so every new gesture competes with it, and that nested-scroll-plus-collapse interaction is where the old tray’s bugs lived. A full-page view gives those features the whole screen and the whole gesture budget. Your video shows a drawer can hold the header row, but it can’t hold the new interaction model.

What’s in flight, against your list:

  • Floating toolbar at the bottom (a Material 3 component, not a new invention): Private / Tabs / Groups / Synced / New Tab within thumb reach, plus a text title on the top bar and search/menu in the familiar Android spots. Nightly soon for additional testing.
  • The few-tabs case is still open (what this ticket is about). Tabs filling from the bottom edge upward, and a tab resize button + gesture, are the two ideas we’re exploring for it. Design only, no code yet. Will post more updates related to this specifically on this ticket.
  • Header position following Address Bar Location, and swipe to switch page types: exploring.
  • Dismissing follows the Android full-page pattern (Back), same as Chrome and Samsung Internet. Tapping your active tab also returns you with no side effects. I do realize there’s a loss of orientation from losing the ability to peek at tabs - tradeoff of persistent context in exchange for the full screen, deeper functionality, and the full gesture budget
  • FYI there’s another designer currently working on menu customization, and we’ll work to get updates on that as well

From here: I’ll post updates in the primary Connect Idea thread, with visuals, APKs, and videos earlier in the process. I'll be sure to give every item a label (exploring / in Nightly / committed)

We deeply appreciate your passion and partnership in driving toward the best experience for all users.

Flags: needinfo?(ryfrazier)

What’s in flight, against your list:

  • Floating toolbar at the bottom (a Material 3 component, not a new invention): Private / Tabs / Groups / Synced / New Tab within thumb reach, plus a text title on the top bar and search/menu in the familiar Android spots. Nightly soon for additional testing.

Please don't do this. Floating tool bars are pretty in a screen shot but a usability PITA. They cover content, can be spoofed by pages, have to deal with conflicts with bottom anchored page elements, force extra padding so the UI can flow around it and are overall distracting as there is unreadable content moving about the control elements.

I know that every AI app seems to do this and outlook does too but it really just says the content is secondary to whatever buttons and controls the designer decided to put front and center. Let page be contained where we know it will be and not mix untrusted content with trusted app functions.

I can see an exception for the home page because that is all app managed controls but when I'm browsing, don't cross the streams.

Flags: needinfo?(josh)

(In reply to Rylee from comment #22)
I owe you an apology Rylee, thank you for detailing and addressing these core concerns with the tab menu (and the new design in general).

The largest part of this frustration (to me) stems from these high-level, irrerversable design decisions being made behind closed doors. For instance, when Nova was revealed for Desktop earlier this year, there were several opportunities for community feedback, which distinctly helped shape the final product before it shipped (useless borders+gaps long gone).

Android's new UX never got that peer review, outside of the nightly channel. If regular users of this browser had an early say in these designs before they were implememted, I highty doubt the design would be as disconnected, obstructive, and obtuse as it is now. It's likely too late to gain trust from the Connect community, but please do engage as planned, and don't discount any feedback from them.


A bottom sheet owns the vertical drag for itself, so every new gesture competes with it, and that nested-scroll-plus-collapse interaction is where the old tray’s bugs lived. A full-page view gives those features the whole screen and the whole gesture budget.

I would like to kindly debate this statement specifically. A drawer is still suited, even with all these new features you noted.

There was never a question in the old drawer on which swipe would scroll tabs (only when swiping tabs themselves), or which would expand or close the drawer (only when swiping on the header). A quick search of Bugzilla on various keywords yields no results for this matter on the old tabs tray, open or closed.

To completely toss out and redesign an element because of percieved issues with gestures makes no sense. However:

Dismissing follows the Android full-page pattern (Back), same as Chrome and Samsung Internet.

This makes painfully clear that the designers (or whichever LLM they are using) want Firefox to resemble Chrome or Samsung (or Opera). Now it makes sense, but please tell me this is actually not the case. Nobody asked Mozilla to clown their designs, surely?

I use Firefox (and still use v148 with the old UX), because they are NOT Chrome or the competitors. The LLMs and people driving them don't seem to consider this.


Floating toolbar at the bottom (a Material 3 component, not a new invention): Private / Tabs / Groups / Synced / New Tab within thumb reach

@JoshH perfectly detailed why this is a bad idea. Please understand that this will not solve the reach issue caused by the full-screen menu.

I will want to disable it immediately as a customization option, and I'm sure many others will too.

Duplicate of this bug: 2069257

Thanks to you both, @JoshH and @breakingspell, for the input. It’s a tricky balance- respecting the expectations and mental models of existing and new users across generations and needs, helping people navigate change, and adding value for everyone. We’re trying our best to do that in a way that helps Firefox continue to thrive and grow.

Unfortunately yes, there have been gaps in early communication and community input. Our team is working hard to improve that, including through Nova and through me and other designers and cross functional partners aiming to share early and often.

On that note, I'll be back soon to post links here in this thread to Moz Connect where I'll be posting early ideas as mentioned before.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: