Patrick Storz Assignee
	Description • 10 years ago

We have implemented "Close Tabs to the Right" in bug 866880.
The logical next step is to also implement an option to "Close Tabs to the Left".

Actually closing tabs to the left might be even more useful than closing tabs to the right:
- In a normal workflow one opens new tabs to the right and
  reads them left to right
- This means read tabs are on the left, unread tabs are on the right.
- One possibly would not want to close unread tabs in this situation
  (close tabs to the right)
- However one would want to close read tabs if they are not needed anymore
  (close tabs to the left)

Another scenario where "Close Tabs to the Left" is more useful than "Close Tabs to the Right":
- Assume you have browsed before and minimized/closed Firefox with pages
  of this session still opened
- You start a new session (e.g. by following a link somewhere) and
  maximize/start Firefox again.
- After having opened some tabs in the new session, you realize you still
  have the pages of the old session (which will be to the left) opened
  but you don't need them anymore.
- You would want to "Close Tabs to the Left" of the first tab of the
  new session.

	Jared Wein [:jaws] (please needinfo? me)
	Comment 1 • 10 years ago

I disagree with the usefulness of "close tabs to the left" (ctl). In fact, over time I've become skeptical at the usefulness of "close tabs to the right" (ctr), however ctr also matches parity with Chrome.

	Patrik
	Comment 2 • 7 years ago

"Close Tabs to the Left" should definitely be an built-in feature. Especially now with the limited Add-On API where there is no way to put this option in the right position in the Context-Menu as an Web-Extension.

Also a common workflow is to pin Tabs like RSS-Reader, Mail, etc. which opens new tabs to the left of every existing tab which you want to keep open usually.

Side note why is all the most used stuff like closing tabs way down in the context menu by default? Makes absolutely no sense.

	Ryan Feeley [:rfeeley]
	Comment 3 • 7 years ago

You might like the add-on FoxyTab. Obviously adding items to the context menu is not free. It’s already becoming quite overloaded. At a certain point (a dozen?) it becomes unwieldy. Do we have any data on which items are even being used?

	Jared Wein [:jaws] (please needinfo? me)
	Comment 4 • 7 years ago

bwinton may be able to get you the details about which menu items are used most. We could use those details for a bug that is focused on cleaning up the context menus overall.

I'm going to close this as wontfix though since the situation described in comment #2 is a workflow that is quite narrow and we haven't had many other requests for this feature in the four years since it has been filed.

	Blake Winton (:bwinton) (:☕️)
	Comment 6 • 7 years ago

Sadly, no, I only have data for context menus in content, not in chrome…

	Pulsebot
	Comment 10 • 3 years ago

Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/29bb42ae7d0b
Implement "Close Tabs to the Left" r=jaws

	Pulsebot
	Comment 12 • 3 years ago

Backout by cbrindusan@mozilla.com:
https://hg.mozilla.org/mozilla-central/rev/791ad465a0c8
Backed out changeset 29bb42ae7d0b for causing bc failures in browser_multiselect_tabs_close_tabs_to_the_left.js

	Pulsebot
	Comment 13 • 3 years ago

Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/539d6c25a60e
Implement "Close Tabs to the Left" r=jaws