Live data from Hacker News

A new spam policy for “back button hijacking”

developers.google.com

221–230 of 532 posts

Re: A new spam policy for “back button hijacking”

#221

Earlier quoted context omitted.

Also www.reddit.com is/was doing the same back button hijacking. From google.com visiting a post, then clicking back and you would find yourself on Reddit general feed instead of back to Google.

I'm pretty sure what you're describing is this long-standing bug[1] I've experienced only when using Mobile Safari on Reddit - affecting both old.reddit.com and the (horrible) modern Reddit. It just doesn't happen in other browsers/engines except on iOS. It's especially annoying on an iPad when I tend to use back/forward instead of open-in-new-tab-then-close on iPhone. [1] At least, I hope it's a bug.

A bug that just coincidentally affects the only reddit visitors that are worth any money?

Re: A new spam policy for “back button hijacking”

#222
post #130

Earlier quoted context omitted.

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

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

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

Re: A new spam policy for “back button hijacking”

#223
post #217

Earlier quoted context omitted.

> You get a link from LinkedIn [or such]. You click on it, the URL loads, and you read the post. When you click the back button, you aren't taken back to wherever you came from. Instead, […] I've taken to opening anything in a new tab. Closing the tab is my new back button. In an idea world I shouldn't have to, of course, but we live in a world full of disks implementing dark patterns so not an ideal one. Opening in…

I do that everywhere, but it seems to fail for LinkedIn: they don’t redirect the link if it’s not in the same tab.

Bad design on their part, another reason not to revisit! If a site breaks my workflow I generally stop using the site, rather than changing my workflow.

Though I'm guessing it would work in the cases being discussed in this article & thread: when you are navigating into a site (such as linkedin) from another, rather than following internal links.

Re: A new spam policy for “back button hijacking”

#224

> Notably, some instances of back button hijacking may originate from the site's ... advertising platform I feel like anything loaded from a third party domain shouldn't be allowed to fiddle with the history stack.

If it happened browsers started to warn their users about third party JS doing back button history stuff, I have a hunch, that many frontendies would just shrug and tell their visitors: "Oh but for our site it is OK! Just make an exception when your browser asks!" just like we get all kinds of other web BS shoved down our throats. And when the next hyped frontend framework does such some third party integration for "…

Your parent commenter didn’t suggest asking for permission, they suggested not allowing it, period.

Re: A new spam policy for “back button hijacking”

#225

Google should actually fix this from the browser side instead of trying to seriously punish potentially buggy sites.

We tried a few times. We got as far as gating the ability to push into the "real history stack" [1] behind a user activation (e.g. click). But, it's easy to get the user to click somewhere: just throw up a cookie banner or an "expand to see full article" or similar. We weren't really able to figure out any technical solution beyond this. It would rely on some sort of classification of clicks as leading to "real" same…

> We tried a few times

Classify history API, canvas etc etc as "webapp" APIs, and have them show a similar dialog to the webcam dialog.

Then I can just click no, and the scripts on the page can't mess around.

Yes Google Maps is great. No, my favorite news site doesn't need that level of access to my browser or machine, it just needs to show some images and text.

Re: A new spam policy for “back button hijacking”

#228
post #220

Great. Can we do ctrl-f search hijacking next. So jarring when websites replace core functionality with their own broken crap because they think they’re special. Some also seem to hijack right click menu now

Firefox allows you to bypass right click hijacking by holding shift before pressing right click.

Re: A new spam policy for “back button hijacking”

#229

Ok, you can start with LinkedIn, I'll wait... If you are wondering how it works. You get a link from LinkedIn, it's from an email or just a post someone shared. You click on it, the URL loads, and you read the post. When you click the back button, you aren't taken back to wherever you came from. Instead, your LinkedIn feed loads. How did it happen? When you landed on the first link, the URL is replaced with the homep…

Also www.reddit.com is/was doing the same back button hijacking. From google.com visiting a post, then clicking back and you would find yourself on Reddit general feed instead of back to Google.

I usually find the back button just doesn't work on new Reddit at all.
Post reply on HN