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

Coming to Chrome: a new way to use tabs

blog.google

Post reply on HN
Print view View original

351–360 of 392 posts

Re: Coming to Chrome: a new way to use tabs

#351

Post by dorian-graph »

klohto wrote: post #100
matsemann wrote: post #29

Earlier quoted context omitted.

Can't remember why, but I ended up using Sidebery instead of Tree Style Tabs. So that's also a nice alternative.

I wasn’t aware of Sidebery, but it looks way better than TST. How is the performance? With TST I notice it doesn’t “hibernate” older tabs (only if you restart FF). EDIT: Damn! I'm blown away by Sidebery. The amount of customization and native looks is awesome. There is only a slight problem when compared to TST: It does not preserve tab grouping when parent tab is closed.

I switched from TST to Sideberry many months ago and have had no performance issues with quite a large number of tabs open.

Re: Coming to Chrome: a new way to use tabs

#352

Post by WorldMaker »

dmortin wrote: post #173
mkj wrote: post #8

Earlier quoted context omitted.

A bit tinfoil hat, but could it be an attempt to head off Firefox Containers which would be a threat to Google Cookie collection? That's certainly my main use case for containers, using Google Music without telling the rest of the web about my Google account.

There is also browser fingerprinting, so they may still know it's you even if you are in a private tab.

And IP (range) fingerprinting.

But the point is don't have to give the easy stuff like cookies away for free to mice like Google. They are still going to beg for milk either way, because they are greedy, but you don't have to be hospitable and keep feeding them cookies. (I mean the number of dumb ReCaptcha's I've had to do has gone way up since sequestering Google apps to their own container. Gross.)

Re: Coming to Chrome: a new way to use tabs

#353

Post by TMWNN »

john_moscow wrote: post #35

This is nice, but what I really don't get is how come the most popular browser in the world in 2020 not have an native option to go through the tabs in the most-recently-used order. This is major productivity improvement compared to ctrl-tabbing the tabs in their physical order. IIRC, multi-tabbed IDEs figured it out somewhere in the 90s and it has become a de-facto standard since then. But nope, Chrome doesn't suppo…

The only extension that I've seen implement this closer to right is CLUT https://chrome.google.com/webstore/detail/clut-cycle-last-us... (specifically, the "Quick switch" and "Normal switch backward" keybindings). Every other one I've tried does not.

I only wish that a) it would visually display the tab history the way Firefox does, and b) being able to shorten the Normal switch backward timer, so I could use that only.

Re: Coming to Chrome: a new way to use tabs

#354

Post by benrbray »

fraXis wrote: post #320
benrbray wrote: post #25

Earlier quoted context omitted.

Wrong! I have a very sophisticated system for managing my tabs. I'm very breadth-first when browsing the web and I also switch contexts a lot. Tabs are like a big Todo list for me. For a while, I would get really frustrated when chrome would crash and close all my tabs, but recently I found a ln extension that keeps track of my tab history as a big tree! Yippee!

What is the name of the extension that you use to see your tab history as a big tree?

Tabs Outliner: https://chrome.google.com/webstore/detail/tabs-outliner/eggk...

Re: Coming to Chrome: a new way to use tabs

#355

Post by jpswade »

snazz wrote: post #303
jpswade wrote: post #286

This is fixing the wrong problem. Tabs aren't broken, browser history is. When I tried to find a web page from a certain date a few months ago, it was almost impossible to find. I actually think Internet Explorer used to have quite a good history. That's what we need, not better tabs management.

Really? Chrome's history search tools are very good, and it's just a SQLite file. I've only had to break out the SQL queries once, but it allowed me to find something very specific. Take a look here: https://gist.github.com/dropmeaword/9372cbeb29e8390521c2

Yes. Really.

Re: Coming to Chrome: a new way to use tabs

#356

Post by Deely123123 »

SparkyMcUnicorn wrote: post #321
deelly wrote: post #305

Earlier quoted context omitted.

Vivaldi Profiles. Only difference is that in Vivaldi each Profile use separate window (as far as I know).

I'm pretty sure it's the same thing as Chrome's profiles functionality. I tried it out for a week, but it's not quite as robust as Firefox container tabs. When I need Chromium, I use Brave.

Yeah, Brave is new Chrome.

Re: Coming to Chrome: a new way to use tabs

#357

Post by Shorel »

0mn1 wrote: post #106
maciekmm wrote: post #90

Earlier quoted context omitted.

Shameless plug. I made the ContainerTabsSidebar firefox addon[0], which is inspired by the TST. It groups tabs based on firefox privacy containers, which means every container has an isolated cookie store. I'm a tab hoarder and developed it to work for such "use-case". It's very similar to the groups presented, but displays tabs vertically. [0]: https://addons.mozilla.org/en-US/firefox/addon/container-tab...

Shameless plug, but Vivaldi does this and so much more natively...since beta however many years ago. Haven't touched firefox since.

But Vivaldi is just another Chromium skin. Chromium skins give too much power to Google.

The entire Web standards should not be regulated by just one company.

I will stay with Firefox.

Re: Coming to Chrome: a new way to use tabs

#358

Post by jedberg »

maciekmm wrote: post #339
YennaV wrote: post #333

Earlier quoted context omitted.

How does your extension interact with Temporary Containers ( https://addons.mozilla.org/en-US/firefox/addon/temporary-con... )? I am a tab hoarder too and I use Temporary Containers to create ephemeral sessions.

It's currently not the best experience as the temporary containers addon creates a container per browser tab which bloats the sidebar. But there's a github issue for it and I've received a couple of requests regarding this today, so I will tackle this ASAP.

I use temporary containers and I installed your add-on. I just checked the box that removes empty containers and it works great!

Your extension has already changed my life and I only installed it last night.

Thank you!

Re: Coming to Chrome: a new way to use tabs

#359

Post by RHSeeger »

wingerlang wrote: post #325
RHSeeger wrote: post #308

Earlier quoted context omitted.

> Top right seems to always have space. Top right isn't always visible when trying to click a window to bring it forward > You can also drag any window from any side by dragging perpendicular to the resize direction. It’s still small but I never heard anyone complain about precision there. Interesting, I hadn't seen that before. It's still a small space and annoying to grab, but it's better than now knowing about it.…

> Not sure what you mean here. I mean automatic tools to move windows. I use BetterTouchTool with a lot of custom gestures to handle my windows. With this I mean for example swiping with 5 fingers to the left moves and resizes the window to take up 25% of the screen on the left side. And so on so forth. I rarely drag my windows around anymore, it's second nature at this point. > I use a mouse and full keyboard. I've…

I'll check it out, thanks. Though I still think just leaving the title bar alone would be a simpler solution. Plus, it means you can see the title, which is nice.

Re: Coming to Chrome: a new way to use tabs

#360

Post by metroholografix »

floatingatoll wrote: post #350
metroholografix wrote: post #311

Earlier quoted context omitted.

Forking to switch a bunch of command line arguments around seems excessive to me. You can simply write a wrapper script that passes the arguments in the way you want them to be passed. Enabling those options does nothing to improve fingerprinting resistance, it's a completely bogus argument. Disabling them however, in combination with the recommended extensions that are in the README plus custom user agent handling,…

Forking permits me to efficiently git rebase against upstream when there are changes, using rerere to remember easy conflict resolutions. A wrapper would not work as two of the options cannot be removed from the command line (and the author refused a PR that would have permitted such a wrapper).

I am the author. Flash support in Chrome is going away soon (but even if it didn't) I am not going to be publishing any code with support for that crap baked in. However, it is understandable if you disagree.

Re: referrer option, as I explained, it's a nop. So no point in having extra code for that there either (I really should remove it).

Post reply on HN