Allow users to manually re-order tabs

[vesta0]

User Story

As a user with a lot of open tabs, I want to be able to easily locate the last tab I was on and re-order tabs in a way that fits my needs, so I don't have to spend time looking for a specific tab.

Acceptance Criteria

• I can easily find and open the last tab I was on
• I can easily re-order tabs to where I want them to be

┆Issue is synchronized with this Jira Task

[ekager]

Relevant - adding lastUsed field to Tabs in AC: mozilla-mobile/android-components#5178
We are going to be working on this very soon as part of Sync Tab work

[liuche]

Currently we put the most recent tabs on bottom, highlight the current tab, and will scroll to tab.

[yoasif]

Currently we put the most recent tabs on bottom, highlight the current tab, and will scroll to tab.

This matches desktop, but I use https://addons.mozilla.org/firefox/addon/always-right/ (browser.tabs.insertAfterCurrent:true) to get tabs adjacent to the position I am at when opening a new tab.

Fenix already opens tabs in an adjacent position when opening a new tab from an existing tab (spawning a tab). I think it would be nice to have the behavior of browser.tabs.insertAfterCurrent:true in Fenix by default.

It also makes more sense with gestures - imagine if a user swipes left on a tab and doesn't find the tab that they just came from (by opening a new tab).

Seems like that is also filed here: #10365

[liuche]

We've done this for MVP, but we'll need to talk about how to handle the different paradigms of: self-ordered tabs vs recent tabs

[Dakkaron]

This feature is enabled in nightly already. We have a product decision to enable it in beta and release also.

Does this mean tab reordering is coming back to the main andoird firefox app? I left a comment here months ago explaining my frustration and that I am not super tech savvy so I am unfamiliar with the lingo.

Any guarantee and timeline?

Thank you.

Disclaimer: Not a Mozilla employee here.

They just pushed a change that removes the feature toggle which, up until now, prevented the feature from showing up in the beta and release (which is the "real") versions. Since this is removed, the feature should show up in the next release of FF.

The next release is scheduled for the 15th of November.

Again, take everything with a pinch of salt, since I am not a Mozilla employee, I know only what I can see publically.

[cadeyrn]

Since this is removed, the feature should show up in the next release of FF.

The next release is scheduled for the 15th of November.

Assuming it will ride the trains it will be in Firefox 108 Beta and then Firefox 108, not in the stable release of Firefox 107 that will be released in November. Firefox 108 is on schedule for the 13th of December.

[SoftVision-LorandJanos]

There is no "Sort open tabs" section in the tab settings in the latest Nightly 108.0a1 (2022-11-03).
Will recheck later.

[Mugurell]

There is no "Sort open tabs" section in the tab settings in the latest Nightly 108.0a1 (2022-11-03). Will recheck later.

The feature ended up having no setting.
There is no automatic functionality, users can do the "long press and drag tabs to reorder" gesture or not.
This was already enabled in Nightly, the recent patch enabled the feature in beta and release also starting with version 108.

[SoftVision-LorandJanos]

With this new information, I can confirm that the tabs can be manually rearranged by "long press and drag" in the latest Nightly 108.0a1 (2022-11-03).
Device used: Oppo Find X5 (Android 12).
Closing the ticket as verified.

[SoftVision-LorandJanos]

Verified as fixed on the latest Beta 108.0b1.
Device used: Google Pixel 4 (Android 13).

[MasterInQuestion]

    Not possible for private tabs.

[Jorengarenar]

@MasterInQuestion I think you may need to create new issue for that

[MasterInQuestion]

    Creating a new Issue for one essentially identical?..

[Jorengarenar]

Creating a new Issue for one essentially identical?..

This one ain't gonna reopen itself and nobody gonna rebase the repo to change commit messages to undo "fixed by".
So yes, this feature request is complete. If you wanna have the bug fixed, report it.