Late last year, after having used it as my daily default browser for a few [maybe several?] months, the incessant bugs, unrelenting workflow-buggering major changes, & frequent loss of all tabs, caused me to abandon
[only in early Beta back then, so not totes surprising] & return to ticktacking back & forth twixt
and
. Into 2025 those latter two continued competing for my daily affections.
T'other day i learned that the long awaited native #TabFolders in
have now landed in #ZenTwilight [the nightly / Alpha version], & thus might be expected to make it finally into the Beta version within a week or two. This morn, possibly against my better judgement but tbc, that discovery inspired me to jump back into my
Beta & relearn it + learn all the stuff new since i last dabbled, in anticipation of this incipient major design UI & UX change.
All the #KleverKids are saying that Zen's TabFolders are a game-changer, coz they will provide users with the first ever native-in-a-Fox browser tab hierarchical nesting. None of
,
, nor
has it [all only flat, not tree, structures; ditto flat-only in Chromium, Vivaldi, Edge et al]. Hitherto the only way to gain this important function has been via AddOns like #TreeStyleTab or #Sidebery. These are both fabulous, but do not have access to all the native foxy code bits n pieces [i've damn well forgotten the proper term atm, sigh], so by using either of these AOs we lose some of the important fox functionality, eg, tab context menu items. If the Zen Dev/s do their work really well, we will finally have our tabby cake & eat it.
β & β
β
#floorp12 beta 12.0.6. Still buggy, yet very usable. My fingers remain crossed for its future. I began using
when it was v9, 10, 11, ie, all based on #ESR. It was my daily default for several months last year, but ultimately i tired of its ESR base & returned to my longterm
#FirefoxNightly. Earlier this year, the moment i discovered the initial public beta of 12, i installed it on lappy & tower. On lappy it's my daily default, whereas on main pc tower Nightly remains default, at least until some of the more impactful bugs / omissions in 12 are solved.Still happily using #Floorp12 Beta as my daily browser, but made an important change last night. As a longterm #TST, then later #Sidebery, user & lover, the last several months of me deliberately forcing myself to use my #FirefoxNightly then more recently Floorp12 Beta profiles predicated on the native FF #VerticalTabs & #TabGroups has been interesting, yet filled with frequent regret, so invested have i been for years in the power of managing all my tabs in a sophisticated tree hierarchy.
FF native tab groups atm remain merely single-level, like Chromium & Vivaldi, thus far less powerful than either TST or Sidebery. I know from bitter experience last year with Floorp10 & Floorp11 that Sidebery is incompatible [due to the Floorp #Workspaces; not only do Sidebery's tabs not recognise/respect Floorp's Workspaces, because both softwares seek to control tab location, they severely clash, causing major browser instability & often tab loss]. Hence i've made no attempt to court further/similar disasters by trying Sidebery in Floorp12. So, last night i created a new profile in Floorp12 for use with TST, & that's what i'm now using. Though in Nightly i regard Sidebery superior to TST, in Floorp the reverse is true; the Floorp Dev/s seem to have taken particular steps to ensure TST compatibility, which thus integrate really well with Floorp's native Workspaces.
The one decided drawback atm of using this new profile however is that with TST active & native tabs hidden, there is no instant access to the important tab context-menu items for splitting-tabs, & moving them to other Workspaces. Fortunately, both those operations i need to use only rarely, so my clunky workaround, which would be untenable if i needed to do it dozens of times each day, is bearable albeit still irritating. When the occasional need arises to do either of those operations, i temporarily unhide the native tabs at the UI top, perform the requisite right-click ops on the applicable tabs, then re-hide said native tabsbar.