If unnecessary complexity as a concept were condensed into code, it would be this obtuse add-on. People like it for the same reason they like VS Code, it has an ecosystem of easily bolted in plugins to geek out over but they aren't adding very much (honestly most should have just been options bolted into the original project) and if willing to use userchrome.js still (yes it can still easily be done, more easily than porting a *.uc.js script to an add-on with either manifest version. Looking beyond the first Google result will not cause you to develop a fatal illness so maybe try it sometime, Reddit hivemind drones!) the whole functionality of this flying spaghetti monster of code can be accomplished in less than 80 lines of JS. The Floorp fork of Firefox implements (and finally effectively fixed their implementation to be usable) this functionality, is not so garish by default (it naturally integrates into the browser style and needs no extra ugly CSS selectors specific to it, what a concept!) and doesn't turn into the hot mess of TST's bad implementation of tag nesting (God forbid you try to rearrange those tabs with a mouse without becoming enraged, tried on Linux and macOS, fickle and badly implemented trash on both ) and doesn't have the "Tree Style Tabs" pendejo banner at the top with the unnecessary close icon (if they don't want it in the sidebar, they probably will just remove the add-on altogether, duh).

I know the hivemind loves this extension and so I will get some virtue signaling indignant outrage for saying this extension is garbage so the brave outraging voice of the people can feel like part of the smart crowd for 5 nanoseconds... but its garbage.

It's a good add-on, but it stops the Option+Shift+Right-/Left-Arrow combination for selecting words from working in the browser on macOS. This is quite bothersome, as this is a very commonly used key-combination.

I really don't understand.
Why does copying (alt+D+enter) a subtab create a new parent tab instead of creating it at the same level?
Please don't update. It gets worse with every update.

2024. 05. 28.

-----------------------------------------------------------------


Problems in previous versions have been fixed.
Thank you for the quick feedback.
This add-on is one of the best add-ons for Firefox.

2024. 04. 20.

-----------------------------------------------------------------


This is a really bad update.
The previously intuitive drag/tree creation method has become truly confusing.

01. In the past, if I dragged a tab and put it inside, it created a new subtree, but now I have to drag it on top or bottoem of the tab to create a new subtree. (It’s different every time. What are the rules?)
02. In some cases I can create a subtree of tabs, but in other cases I cannot create a subtree of tabs. It becomes really sensitive when dragging.
03. It is not possible to create a new tree by dragging a child tab that does not have child tabs.

(There's more, but that's all I remember...)

What is the reason for this update??
Instead, it has become really, really confusing.
It would be nice to roll back. At first I thought there was something wrong with Firefox.

The usual tree style tab is 5 stars.
But I'm giving it 1 star because of this update.

2024. 04. 04.

This extension has been great for a very long time. Easy 5 stars.

The latest update has made it borderline unusable though.
How do I create a new tree? It seems to be completely random, sometimes they just pop up. But dragging one tab onto another seems to be impossible.

In past times I even removed the builtin tab bar. Right now I am seriously considering to remove the addon until the situation is fixed.


EDIT: I have briefly seen, how it's supposed to work. That is all fine.
But there seem to be major bugs right now. Most of the time, like described above, it's not possible to drop a tab onto another tab to create a tree. Also there are super weird interactions between page content and tree pane.
I have disabled the extension for now. Hope to see it back in former glory soon.

firefox keeps crashing after installing the extension.

This has not worked in more than a month. It just loads forever and never works. It used to work perfect. Please fix it.

не работает, просто зависает панель вкладок и висит. нашел решение доп-ние "Sidebery", https://addons.mozilla.org/ru/firefox/addon/sidebery/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

Suddenly stopped working. Mac Sonoma 14.2.1, FF 122.0 (64-bit)

This is a great extension, one that I've been using for years, but the last update has MAJOR problems. It stoppped working on Firefox ESR 115.7.0esr (64-bits), the workaround suggested by its creator didn't do anything. On Firefox 122.0 (64-bits), the extension was apparently ok, but then I used that workaround giving permissions to "Read and modify bookmarks" preemptively and all my bookmarks were gone. DO NOT USE THE WORKAROUND.

Since the last update (3.9.20/jan 2024), extension slowed down everything, transforming FF in a memory eating black hole.

Please debug ASAP.

Rolled back to 3.9.19 and everything seems to be fine!

Раньше было более-менее нормальное расширение, а с последним обновлением это просто невозможно стало использовать. Жрет память как не всебя. За 7-10 минут использования и перехода по 10-15 вкладкам из 150 сожрал 23 ГИГА ОПЕРАТИВКИ, причем все остальное (дополнения и открытые страницы) уложилось в 4 гигабайта оперативки.

J'ai utilisé l'extension durant 3 semaines et depuis 1 semaine, l'extension à des fuites de mémoire
Ayant l'habitude de jouer avec une page web en fond, cela à fait planter mon pc à plusieurs reprises avant de trouver la cause du problème. C'est inutilisable actuellement et je suis passé à une autre extension.

I estimate that TST, all by itself, nearly doubles Firefox's memory footprint. Sidebery freed up 5-10G of memory for me by comparison (yes, way too many tabs...). TST should *not* be a recommended extension. Latest update of TST leaks memory *very badly* and crashes, taking other Firefox extensions and other desktop programs down with it when the OS starts killing things to free up memory. Sidebery is *much* more responsive & performant with a very large number of tabs. This alone will remove a huge amount of friction in reducing the number of open tabs. No more waiting for TST to catch up. Switching to Sidebery was no problem: all nesting retained. Disable TST. Install Sidebery and verify ok. Remove TST. Done.

virus

Unable to bookamrk

after using ~one mouth going between tabs is lagging so it`s impossible to use