Firefox 145 drops support for 32-bit Linux, marking the end of an era
https://fed.brid.gy/r/https://nerds.xyz/2025/11/firefox-145-better-privacy-pdf-notes/
so have had this for a while, & it is certainly helpful. overall though, until we get nestable groups, thus facilitating in effect tab trees, this belated advent of foxy #tabgroups remains inadequate for me, ergo each day i continue to use my #TreeStyleTab profile not my #NativeVerticalTabs profile.Firefox 145 drops support for 32-bit Linux, marking the end of an era
https://fed.brid.gy/r/https://nerds.xyz/2025/11/firefox-145-better-privacy-pdf-notes/
Well, that's inelegant. I mostly use the Simple Tab Groups extension in #Firefox and tried the newer built-in Tab Group function, which is totally different. They don't play well together.
Visually, #SimpleTabGroups really works more like the different virtual tab bars #Sleipnir uses. I use ten STGs in Firefox. What I was looking for was tab stacking more akin to #Vivaldi, where stacks stay on their starting workspace/tab-group/tab-bar.
But no. With Firefox #TabGroups, the labels for new groups show up on all the simple tab bars (workspaces/tab-groups). Yet the tabs within the inbuilt groups don't. Inconsistent.
Look at the bar under the "y" block. That means that group is expanded, but since the tabs within it are from my blue tab bar, they don't show up on my red tab bar (identified by the circle before the address bar).
So it seems Tab Groups fail me. If someone was not using grouping in one of the ways already possible, they might be a nice addition. But they don't cooperate with the way I already used. They should have been a flourish, but to me they're a flop.
I've just discovered that I can not only *name* the #Chrome tab groups on my phone, but can also *colour* them.
Nice.
Now I know where things are by name and pointless colour choice
Recently discovered Firefox's tab groups, which probably have been there for years without me noticing 💡
I would once again like to thank the #Mozilla folks for their fine work on making #Firefox do what they think the user should want, rather than what the user actually wants. This is a challenging technical task, but they have proven to be very adept at it over the years.
Current #gripe: tab groups. My tabs just started opening in tab groups without me doing anything. Took a while to figure out this was actually what was going on; the UI affordances for this are not obvious, and it just seemed to be two unrelated niggles - (1) links opened in new tabs weren't opening at the end of the tab bar, and (2) some weird little thing was showing up in the tab bar, which just looked like a graphical glitch.
I didn't enable tab groups, but I suddenly got them anyway.
I didn't choose for links opened in new tabs to be placed into tab groups, but I got that anyway.
And there's no setting in the UI to control this, at least in my Firefox. Search the settings UI for "group" and there's 0 results. Looking through the settings, I don't see it under another name.
You can turn it off in about:config - it's at `browser.tabs.groups.enabled`.
Firefox keeps getting worse and worse. This "we know better than the user, they should want this change and we won't let them even opt out, much less require them to opt in" is a huge driver of that.
When will #Servo be suitable as a daily driver?
#tab #BrowserTab #TabGroup #TabGroups #browser #arrogant #PissesMeOff #PissMeOff
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.
Ich hoffe, ich lehne mich nicht zu weit aus dem Fenster.
Tab Groups werden einen ähnlich großen Einfluss auf meine Arbeit mit dem Browser haben, wie damals die Einführung von Tabs an sich.
@MsDropbear42 @floorp Well well well, how nice! 💃💃
Floorp Daylight aka Floorp 12 Beta, Version 138.0.2@0.1.21 as available 11 hours ago at https://github.com/Floorp-Projects/Floorp-12/releases/tag/beta, has made a major jump forward in features & reliability.
Atm the native #Firefox #TabGroups do not respect Workspaces, ie, persist across all of them, unlike ordinary tabs which now do stay in their respective WS. Thus my next focus of interest will be to see if coming Betas manage to fully integrate these Groups into the Workspaces.
TLDR: This latest Beta is such that i can now seriously consider the possibility of using it as more than just a curiosity, & as an actual daily browser.