Known internally as "historical manipulation," it's something Google engineers have had in its sights for a while. Now they have prepared a way for the system to reliably check whether the trick is in use at a particular location.
At this stage, it's an experimental process, only shown by Chromium, and any positives are easily labeled to the user and the data is sent back to Google for analysis.
It is also worth pointing out that a Chromium code obligation does not make a chrome function and there is a chance that this will never see the light of day in its current form, regardless of the fact that it is very "on message" for Chromes latest updates.
In recent months, we have completely banned any form of "suspect" ads, penalize unencrypted sites, Symantec certificates, and of course, Chrome has led to the loss of Adobe Flash (and good riddance).
As ever, Chrome goes through three stages – Dev, Canary, Beta before striking Stable, which means that it should be at least three months before this feature is available to the public, and most likely a bit longer than it's self, but It's good to know that Chrome is still looking for new ways to make us all so little safer.
In the meantime, you will know if it's live, if you feel insane enough to watch the flag menu – it will look like this: # enable-skip-redirecting-entries-on-back-forward-on μ