Please work on tab grouping instead!
this post was submitted on 12 Feb 2024
580 points (97.9% liked)
Linux
48090 readers
754 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Now this would be useful.
It was useful 8 years ago when they removed it, that’s for sure.
Tab groups where natively implemented?
Yes, they worked differently than the way Edge or Chrome do now and were in many ways superior for tab management, much more like Vivaldi’s sessions but more intuitive. I was a heavy user and so am biased. They said “just use an extension!” but it would crash and lose your session (and imo the extension works even worse today). It was really ahead of its time.
Few people used it because they didn’t advertise it or make it easily discoverable. You had to know the shortcut already through osmosis or drag the button out of the customize menu.
load more comments
(4 replies)
load more comments
(9 replies)
Or tabs not crashing when you want to move them between different windows.
I really hope you can turn this off
There'll be a setting in about:config no doubt.
Indeed. I get there are people who probably like this feature, but not me.
I'm tired of Mozilla pushing UI changes on people just for the sake of "progress".
...especially when they don't bother to fix years (sometimes decades) old bugs.
load more comments
(6 replies)
If this defaults to on, I’m turning it off.
Out of curiosity, why? If it's a knee-jerk reaction to change that's completely understandable, but I can't see anything to dislike about the feature itself
I can already read the title of the page and see the favicon, so it actually doesn't show new information. If I accidentally move my mouse there it covers a big part of the page i'm looking at
If you have many tabs opened:
I can already read the cropped title of the page and see the multiple favicon
load more comments
(3 replies)
load more comments
(3 replies)
Not OP but I’d do the same, for the simple reason that I find most overlays super distracting. It immediately triggers a need to see what’s underneath.
On top of the fact that those previews are annoying as hell as other comments pointed out, I want to add that this kind of feature also uses a fair amount of processing + memory.
I think that is a nice opt-in feature for those who wants it but I like my default light and simple.
I think it’s more that there really isn’t a need for this. If I’m not sure what a tab is I can always click on it. Chromium got this a while back and (even with minimal exposure to Chromium) I didn’t like it, it weirdly felt annoying and unnecessary.
load more comments
(4 replies)
This has been people's reactions to anything good that comes into Firefox for close to 20 years now
Really? AV1 & webp support, Quantum engine, process-per-tab, reader mode, HTTP/2 & HTTP/3 support, cross-site tracking protection...?
Browsers have a lot of features. Some convenient, some come and go. That's ok.
Firefox is an ideological choice for some people so both cynicism and unconditional support is expected.
load more comments
(1 replies)
load more comments
(4 replies)
load more comments
(2 replies)
This is not even close to the worst thing they have ever done, but stuff like this is a waste of resources. People mostly want official vertical tabs and more than anything engine performance improvements. (and the ability to pretend to be Chrome in Youtube)
load more comments
(5 replies)
This was already a thing for ages until they killed it, but it is still possible if you are okay with tweaking userChrome.css
Why Mozilla wastes resources on their own implementation instead of providing API's to third party developers is beyond me.
Your first link is based on XUL, which was deprecated because it was wasting resources being unmaintainable and insecure.
Here's a great article about that
load more comments
(3 replies)
This is quite useful, especially for those sites without meaningful or distinctive names.
I miss the days with Opera. Not only could it group tabs, but it had previews too. Mouse gestures. Keyword searches. Page link filters and batch operations. RSS-reader. Chrome didn't even exist back then, and IE and Firefox are still playing catch up. Kinda amazing to think about it.
Vivaldi is the spiritual successor, but having to use chromium rendering engine, it's so many concessions and steps back. Has the mouse gestures, tho.
load more comments
(6 replies)
I think many people in the comments suffer from some version of curse of knowledge.
Sure, this feature us quite irrelevant for a power user who is quick to navigate the browser and needs a split second to remember what tab it is simply by reading the header and seeing the icon.
However, many less proficient people can benefit from this feature. Not once I saw how someone who has 10 tabs open and needs to go to a different webpage, starts meticulously clicking through every single one of them because they have no idea how the page they are looking for is called, they are too overwhelmed by using web as a whole to take notice.
Power users love to bash accessibility features like this. Its a classic case of "I don't need a wheelchair ramp so i dont know why the library added one!"
Accessibility is way more than screen readers. It's more than specific disability-minded modes. The web needs to be friendly to everyone, including people who may not know they could benefit from accessibility features. Everyone benefits from this type of work.
There are definitely some legit feature concerns and priorities being called out here. Mozilla has left a lot to be desired of late on that front. But a power user is more than capable of jumping into settings or about:config to turn things like this off, or finding an extension to get by for now.
Also the firefox dev team isn't tiny. This isn't blocking other work or anything in a substantial way, it's a fairly isolated piece of UI, and there's no guarantee that skipping this would change the timeline on anything else.
load more comments
(10 replies)
Have they ever said if vertical-tabs is a feature they will add? Vivaldi and Edge both support it by default and it's awesome.
load more comments
(5 replies)
1000ms delay seems to be little too much to my liking, changed browser.tabs.cardPreview.delayMs to 500 and it feels much better.
Preview is pretty short for some reason, it might be related to my monitor (32:9) aspect ratio?
I'd rather have them work on fingerprint spoofing, and getting rid of the tracking from google they put into it
Librewolf, if you want to use a firefox based browser, use librewolf instead.
"We're super excited to announce that we're working on a feature that has been requested by no one ever".
Not a bad feature IMO....
load more comments
(1 replies)
I love tab previews, but I would hate to give up vertical tabs for it. If they would implement vertical tabs + previews, I for one would be happy.
Anyone know a way to mimic Brave vertical tabs with preview? I can get close, but without preview images and that's what I'm after.
Yeah I always turn off that previi crap immediately as it usually gets in my way of doing things. Please don't even spend time on this feature, I don't really see the use
I don't see the point personally but I enabled it just because and while it does work it's currently very slow for me. It takes around 1 sec for the preview to appear so finding something by moving the cursor quickly across the tabs is impossible unless you slow way down.
From the article:
To control how fast/slow tooltips appear modify
browser.tabs.cardPreview.delayMs. This is set to 1000 (milliseconds) by default, meaning tooltips only appear once you’ve hovered over a tab for at least a second.
load more comments
(1 replies)
view more: next ›