3 ms·
I have always done this, although mostly so I don’t have to reload the page I am coming from when I hit the back button.
by cortesoft 6mo ago
I have always done this, although mostly so I don’t have to reload the page I am coming from when I hit the back button.
- dspillett 6mo agoThis too. Particularly required for broken SPA-style sites that reset when you re-enter instead of properly maintaining their state, or infinite scroll based pages that don't remember where you scrolled to/through.
- Baljhin 6mo agoMany years ago I was 'converted' to browse like that, one of the reasons was just that - to prevent back-button fatfinger. Here's the setup I use: [1] install this userscript, keep the default `include` i.e. 'every link": https://greasyfork.org/scripts/12367-open-links-in-new-tab https://greasyfork.org/scripts/12367-open-links-in-new-tab; add to the `exclude` section the sites from [2]. [2] install this one and turn OFF the default: https://greasyfork.org/scripts/4416-open-links-in-current-tab https://greasyfork.org/scripts/4416-open-links-in-current-ta...; add any sites you want to stay in the same tab to the `include` section (e.g. see [0]). Depending on how you browse, this will be a small list. You can couple this with a tab-memory addon: example-- set [1]-Tabs to 'sleep' after a certain time; that way they're not using resources but still available later. AND if you decide you're not gonna read those tabs anyway, just manually close them with having to activate them. [0] https://news.ycombinator.com/item?id=47763404 https://news.ycombinator.com/item?id=47763404