Google engineers are currently working on a Chrome browser update that will block malicious websites from hijacking the browser's history and, indirectly, the Back button.
The issue at hand is a well-known tactic, often seen employed by many shady sites across the Internet. A user would visit a website, then he would accidentally click or tap on an ad, and be taken to a new page.
But when the user presses the Back button to go back to the previous page, the browser just reloads
Under the hood, dette skjer fordi skadelige sites vil udføre titler eller "redirects" i retning af samme URL, effektivt forgiftning i browserhistorien med samme link , and rendering the Back button useless.
In another tactic, even if websites do not hijack the user from his normal web navigation, they secretly insert ad pages inside the browser history list.
But, recent source code updates [1
These code updates will allow Chrome to detect when browser history entries have been generated by user interaction, or by an automated method.  Also: Brave is the default browser on obscure HTC crypto-phone CNET | Microsoft's Edge to Morph into a Chromium-Based Browser TechRepublic
During an initial testing phase, Chrome will only mark and report these fake history entries to Chrome engineers, so they can analyze the various ways Chrome's history is being abused in the wild.
The endgame is to block or skip these "fake history entries" altogether, according to 9to5Google, the Google-centric blog that first spotted these updates.
However, Chrome engineers have told ZDNet that they are treading lightly with this new feature. De forklaringer er at de ikke vil at implementeringen skal misfire og flaggere browserhistoriske poster som "Back-Button Hijacks," og senere fjerne dem fra browserens historieliste.
Man kan nemt forestille offentligt backlash og "censoring" accusations Google would face if this new security feature goes even slightly wrong.
For now, this new feature is at a "under development" phase, but it is expected to land on the chrome: // flags page somewhere in Q1 2019.