[brchr]

One of the most crucial parts of my reading workflow is opening things in new tabs. (It allows one to explore a topic by BFS rather than DFS.) Asking me "Don't you want to use our app?" is like asking, "Don't you want your browser to only support a single tab?" The answer is no...for all the reasons browser makers discovered in the 1990s.

[dvfjsdhgfv]

For the same reason hijacking links to other pages via JS is an abomination that should be cursed and banned. Each time I click a link to open the link a new tab and see about:blank instead the designer should receive a slap on the wrist.

[mockingbirdy]

I agree, I'm a BFS guy, too (I like that word, very good description). This behavior is a major PITA. With the introduction of JS frameworks in all kinds of cases (e.g. static blog generators that use react), there's the possibility that the developer messed up the routing or deep linking or even forgot the whole feature because he never opens links in new tabs. I have the presentiment that this will happen a lot in the future.

Even m.facebook.com has this problem in the event overview. There's no way to open nearby events in a new tab because the link only works due to JS hooks.

[megaman22]

If you're implementing links with a JS onclick event of some flavor, instead of an <a href="...">, you should be hung up in the street by the toes. There's no excuse for making things more difficult on yourself, in a way that breaks the way things are supposed to work.

[naibafo]

To be fair, there are a few single-tab browsers out there, where you then defer tab management e.g. to your window manager on linux: * https://www.uzbl.org/ * https://surf.suckless.org/