tab-stash VS scroll-to-text-fragment

I like the the https://josh-berry.github.io/tab-stash/ extension. Not exactly what you want, but IMO a very well-done extension in that space.

Firefox handle lots of tabs very well though since the tabs are lazily loaded. Only issue is that the session system once in a while mess up and you lose everything.

If you need vertical tabs, my new favorite solution is Tab Stash in the sidebar.

Tab Stash

I migrated from Sidebery to Tab Stash [0]. I found the user experience to be a bit more streamlined; I don't find myself missing the tree-style structure, but the stashes it provides are a good replacement.

[0]: https://github.com/josh-berry/tab-stash

tab stash is a pretty decent extension for quickly saving tabs and then restoring them later with one click

https://github.com/josh-berry/tab-stash

and unlike some other tab management extensions, it uses native bookmarks to store things which means you can still access the stashed tabs if you sync them to firefox mobile

There were some privacy concerns, regarding leaking of user information: https://github.com/WICG/scroll-to-text-fragment/issues/76

This doesn't make sense. There is no mystery about how scroll-to-text fragments should work. They're documented e.g. here: https://github.com/WICG/scroll-to-text-fragment

It's call "Text Fragments", and it was introduced to Chrome more than one year ago. https://github.com/WICG/scroll-to-text-fragment

I think it works in Chrome and Edge, but not in Firefox.

I kind of want to be able to upvote this post three times: once for the actual projects (which sound really cool!); once for introducing me to the term/joke "rakit"; and once for teaching me about the scroll to text fragment API – I had no idea that was a thing!

The most disturbing example of this I found recently is the new auto-highlighting feature Google proposed to the W3C then YOLO'd into chromium before people's concerns were met, because they have control of it and don't need industry approval to get that to happen. Here's an example convo with some of these topics raised.

Per web.dev, it is for Chromium based-browsers and other browsers have not signaled intent to support. This is quite a rabbit hole. Very recently there has been some spec discussion if you follow links in the pages I've linked here.