Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox tab groups are here

blog.mozilla.org

Post reply on HN
Print view View original

151–160 of 455 posts

Re: Firefox tab groups are here

#151

Post by orbital-decay »

mulhoon wrote: post #129

I know this sounds crazy, but has any browser just tried implementing two (or more) horizontal rows of tabs? - the user can decide to put them up the top or on the second row based on their own prioritising. Or just zip them up. Not saying it’s a great idea but these kind of horizontal chrome groups never worked for me, and Arc tabs are too vertical for me.

>I know this sounds crazy, but has any browser just tried implementing two (or more) horizontal rows of tabs?

Yes. Firefox.

(it was like that long ago)

Re: Firefox tab groups are here

#152

Post by AbuAssar »

Great news, I use tab groups daily in Safari and recently in Firefox beta.

In Firefox, tab groups work better with a vertical tab bar.

In Safari, there is a feature that I wish comes to Firefox: that the tabs in each group act as bookmarks, i.e., they persist across browser restarts and new windows. They are always there within their group; only the tabs that are not in a group are volatile.

This makes tab groups more useful, as you don't fear losing them no matter what.

Re: Firefox tab groups are here

#153

Post by ksec »

seltzered_ wrote: post #135
ziddoap wrote: post #80

Earlier quoted context omitted.

> Wouldn’t each one still use up some memory Firefox unloads tabs that haven't recently been used, or as memory approaches system limits. You can also manually unload your least-recently-used loaded tab.

Yes, but in practice I've experienced Firefox (at least under linux) getting killed by the OS when RAM runs low. I recently lost some low-priority reading projects after I couldn't recover the tab sets (they were opened months ago, so hard to dig back through history) I've found myself using Sidebery and the manual 'unload' tab option quite a bit.

Interesting, because out of all the three browser Firefox should be the best at memory management, unloading tabs along with Sessions recovery.

But I have only ever used it on Windows and Mac. So no idea about Linux. You can do About:memory to check out which tabs are using more memory as well as manual memory compact.

Firefox also allows unlimited History, unlike Chrome which I believe you cant even have history for more than 90 days.

Re: Firefox tab groups are here

#155

Post by Spunkie »

surajrmal wrote: post #19

Why did it take so long? It was their number one request for 3 years and chrome pushed this feature nearly 5 years ago. The design looks like a straight copy of chrome so it's not like there was a large design process to work out. It feels like it was finally prioritized so that they could "improve" it with ai, similar to what chrome is doing.

I think it was just stubbornness, pure and simple.

Firefox actually had a feature like tab groups a long time ago. It was removed for "low usage" and ever since then they have been resisting reimplementing it.

Anyways it still needs improvement but I am very happy to see this finally land. At work we have been moving everyone off of chrome after the manifest v3 shenanigans and the lack of tabs groups was a long standing sticking point for some users.

Re: Firefox tab groups are here

#156

Post by BuckRogers »

fikama wrote: post #20

It's just a clone of chrome feature. Cool they impelmented it too. I just don't see this "we listen to the community" more like "we are just trailing behind chrome"

I used FF for 20 years and moved to Edge a few years ago. I thought similar about this feature, Edge has had tab groups and vertical tabs for a long time now.

Re: Firefox tab groups are here

#157

Post by dizhn »

What a roller coaster ride of a post. Great job guys. No mention of whether the feature is available now on a stable release. What release version that is. How to enable it. How to actually use it. Where to go for documentation or bugs. And congratulations on concentrating on the one top feature request. What's next? Looking at some of the 20 year old bugs that still exist?
Post reply on HN