Have you ever ever been to an internet site the place the again button simply would not work? In these cases, you press “again” to return however as an alternative you simply find yourself on the identical web page the place you began. A brand new commit on the Chromium supply (first noticed by 9to5Google) outlines a plan to cease bizarre web site schemes like this, with a lockdown on “historical past manipulation” by web sites. The commit reads: “Entries which might be added to the again/ahead listing with out the consumer’s intention are marked to be skipped on subsequent again button invocations.”

The again button strikes backward by way of your Internet historical past, and, together with the shut button, it is probably the most frequent methods of leaving an internet site. That is very dangerous in the event you’re a shady web site designer, and websites have tried to mess with the again button by including further entries to your Internet historical past. It isn’t laborious to do that with a redirect—think about loading from a search end result, which immediately redirects you to Each pages would get saved in your historical past, so urgent “again” from would ship you to, which might redirect you once more and add extra troublesome historical past entries. This does not make it unimaginable to depart (shortly hitting the again button twice would possibly work), nevertheless it does make it more durable to depart, which is the top objective.

To cease this sort of historical past manipulation, dangerous historical past entries will quickly get a “skippable” flag, which suggests the again button will ignore them when it navigates by way of the historical past order. One commit says Google nonetheless must give you some form of “pruning logic” to declare an internet site as skippable, however that would most likely be performed with one thing like a timestamp. You spent zero seconds on that redirect web page, in order that’s most likely not a superb historical past entry.

This function has been tossed round as a Chromium bug report for 2 years, however, with commits actively occurring now, we would see it pop up in a nightly Chrome Canary launch quickly.


Please enter your comment!
Please enter your name here