Comment by dpkirchner
6 hours ago
I think this rule is quite unfortunate. Wouldn't we all be better off if sites that hijacked back buttons were just banned or at least had their posts hidden until they're fixed?
Sure, they're somewhat common issues, but so are ads for malware served by Google. Surely we should call those out?
It would be crossing a line for us to ban or penalize sites in response to complaints about the back button.
In this particular instance, it works fine for me on Chrome. When I test it in Safari, I can see the same behaviour that people are complaining about, but I also find that if you double-click the back button, it takes you back to HN.
I point that out because it seems clear to me that the site author has not set out to implement a “dark pattern” to trick visitors into staying on their site against their will; they've just tried to implement some in-page navigation, and perhaps only tested it in Chrome.
That's outside the boundary of reasonable grounds for us to penalize a page or site. It puts us in the position of having to investigate a page's behaviour in different browsers and to adjudicate on the severity of the dysfunctional browser behaviour and the author's intent (i.e., their inner thoughts). We clearly can't be getting into that; it takes up too much time and we will never be able to consistently get the judgments right and provide fair decisions.
I can understand the frustration, but as well as asking HN users not to fixate on offtopic distractions like this, we also ask people to "assume good faith", and I see no reason not to follow that guideline in this case.
A quick email to the author would have more likely led to a favourable outcome than this meta-subthread.
Honestly, I feel like browsers should handle this.
Sites are always going to do malicious shit. The browser should know that when I hit the back button I want to go to the place I clicked that brought me here. SPAs have severely perverted this simple idea, but I’m sure browser devs can figure it out.
It was really just a bad design decision that was exploited. It should be deprecated and removed. Allow it on intranets or some legacy website specific setting, but it should be blocked on the public internet.