A new spam policy for “back button hijacking”
developers.google.com
A new spam policy for “back button hijacking”
1–10 of 532 posts
Re: A new spam policy for “back button hijacking”
#2Frustrating it took this long for something to be done about this, but glad its now got something being done.
Re: A new spam policy for “back button hijacking”
#3Some Microsoft sites have been very guilty of this. They are the ones that stick in my head in recent memory.
Re: A new spam policy for “back button hijacking”
#4The iron law of web encrapification: every web feature will (if possible) be employed to abuse the user, usually to push advertising.
Re: A new spam policy for “back button hijacking”
#5Cool, now maybe let's do something about all the shit I have to clear out out my face before I can read a simple web page. For example, on this very article I had to click "No thanks" for cookies and then "No thanks" for a survey or something. And then there was an ad at the top for some app that I also closed.
It's like walking into some room and having to swat away a bunch of cobwebs before doing whatever it is you want to do (read some text, basically).
Re: A new spam policy for “back button hijacking”
#6Some Microsoft sites have been very guilty of this. They are the ones that stick in my head in recent memory.
Epic store makes it impossible to navigate backwards from the checkout on mobile at least. Not sure if it's design or just poor design.
Re: A new spam policy for “back button hijacking”
#7The iron law of web encrapification: every web feature will (if possible) be employed to abuse the user, usually to push advertising.
It really comes down to JavaScript. The web was fine when sites were static HTML, images, and forms with server-side rendering (allowing for forums and blogs).
Re: A new spam policy for “back button hijacking”
#8Some Microsoft sites have been very guilty of this. They are the ones that stick in my head in recent memory.
Are they? This seems about deceptive or malicious content (i.e., redirecting to ads) rather than “something in my history triggers a JS redirect”. I’ve definitely experienced the latter with MS, but never the former.
Re: A new spam policy for “back button hijacking”
#9Are they considering all uses of window.history.pushState to be hijacking? If so, why not remove that function from Chrome?
Re: A new spam policy for “back button hijacking”
#10Now do paywalls next.