[zozbot234]

The fix is to hold down the back button so the local history shows up, and pick the right page to go back to. Unfortunately, some versions of Chrome and/or Android seem to break this but that's a completely self-inflicted problem.

[Rygian]

That's not a fix. It's a workaround.

[zozbot234]

It's a fix because it completely solves the issue on any site, without requiring changes from LinkedIn or any other actor.

[vitro]

My car leaks oil. So I refill it here and there. This fixes issue with any car maker and does not require action of any other actor.

[nkrisc]

Yes, it’s a workaround because it doesn’t require anyone to fix the issue.

[Spare_account]

>it completely solves the issue on any site

It doesn't solve the problem with Instagram links, which in my experience do the following:

1) Open a new browser tab, with no history. 2) Close the original tab, so I can't easily get back to where I was.

[zozbot234]

That's a different kind of dysfunction, though. You can address it by copying the link and pasting it in a new tab, or if that's not possible, copying the current page to a new tab and clicking on the link there.

[jdwithit]

I've noticed that on Instagram, too. Absolutely infuriating.

[marak830]

It's a work around to them making changes to deliberately change the expected results of pressing "back"

[TeMPOraL]

It's also not a very effective workaround, because some of the websites in question end up spamming multiple instances of their home page in the history stack.

[zozbot234]

You can usually address this by going back as far as possible, then holding the button again so more of the history shows up. And IME, it's only really broken sites that have this problem in the first place.

[TeMPOraL]

Yes, but that's super annoying and at that point graduates to being a shitty workaround.

[neya]

The fix is to not to implement anti-user patterns. What you're describing is a loophole around it.

[zozbot234]

> The fix is to not to implement anti-user patterns.

That's not a fix the user can implement themselves. Holding down the back button is comparatively trivial.

[lxgr]

Why on Earth would the user be expected to implement a fix for a problem they didn't cause themselves in the first place?

[zozbot234]

Why the Earth should the user not want to implement a fix/workaround/whatever for a problem they didn't cause themselves but can trivially solve?

[lxgr]

Because I expect my browser to work for me instead of having memorize workarounds for the new web annoyance of the day.

Clicking "back", noticing that the site broke it, moving the mouse and long-pressing "back" (I normally navigate with a mouse thumb button or a trackpad gesture) is much more annoying than my browser just preventing this from happening in the first place.