Back button hijacking wouldn’t be a problem on first place if the HTML standard (ooopsie, HTML plus JS plus CSS plus kitchen sink!) wasn’t such a bloated mess because of corporations like Google, who tried (and managed) to make the internet more corporation-friendly and thus user-hostile, while raising the barrier of entry for browsers.
So, Google is pretending to solve the problem itself was [partially] responsible for creating. And, in the process, it can control the web from both sides, right? As both the one “graciously” granting the cattle/users access, and the one dictating its access.
For a start: a lot of those rely on the browser history API. Sites should not be granted the ability to manipulate your browser’s navigation at all, be it through JS or smoke signs or whatever. Why is this capability there on first place dammit.
Back button hijacking wouldn’t be a problem on first place if the HTML standard (ooopsie, HTML plus JS plus CSS plus kitchen sink!) wasn’t such a bloated mess because of corporations like Google, who tried (and managed) to make the internet more corporation-friendly and thus user-hostile, while raising the barrier of entry for browsers.
So, Google is pretending to solve the problem itself was [partially] responsible for creating. And, in the process, it can control the web from both sides, right? As both the one “graciously” granting the cattle/users access, and the one dictating its access.
For a start: a lot of those rely on the browser history API. Sites should not be granted the ability to manipulate your browser’s navigation at all, be it through JS or smoke signs or whatever. Why is this capability there on first place dammit.