Have you ever been to a site where the back button just does not work? In these cases, press "back" to return, but instead you only end on the same page where you started. A new commitment to the Chromium source (first discovered by 9to5Google) outlines a plan to stop strange webpages like this, with a "history management" of sites. The obligation reads: "Entries added to the return / forwarding list without the user's intention are marked to skip on subsequent return buttons."
The backspace moves backwards through your weblog, and with the close button it's one of the most common ways to leave a site. This is very bad if you are a shady site designer and websites have attempted to rotate with the back button by adding additional entries to your weblog. It's not hard to do this with a redirect-imagine loading example1
To stop this kind of historical manipulation, bad records will soon get a "jump" flag, which means that the back button ignores them as they navigate through the story. An obligation states that Google still needs to come up with some sort of "pruning logic" to declare a site as hopable, but it can probably be done with something like a time stamp. You spent zero seconds on the redirect page, so it's probably not a good story entry.
This feature has been thrown around like a Chromi error report for two years, but with commitments going on actively now, we can see it coming up in a nightly release of the Canary Islands soon.