Results 1 to 5 of 5

Thread: Google Chrome wants to stop back-button hijacking

  1. #1
    #DeSantis2024 Teh One Who Knocks's Avatar
    Join Date
    Jan 2011
    Location
    5280' Above Sea Level
    Posts
    256,044
    vCash
    10966
    Mentioned
    20 Post(s)
    Thanks
    23,810
    Thanked 113,085 Times in 59,902 Posts

    Cool Google Chrome wants to stop back-button hijacking

    Ron Amadeo - ars TECHNICA




    Have you ever been to a website where the back button just doesn't work? In these instances, you press "back" to go back but instead you just end up at the same page where you started. A new commit on the Chromium source (first spotted by 9to5Google) outlines a plan to stop weird website schemes like this, with a lockdown on "history manipulation" by websites. The commit reads: "Entries that are added to the back/forward list without the user's intention are marked to be skipped on subsequent back button invocations."

    The back button moves backward through your Web history, and, along with the close button, it's one of the most common ways of leaving a website. This is very bad if you're a shady website designer, and sites have tried to mess with the back button by adding extra entries to your Web history. It's not hard to do this with a redirect—imagine loading example1.com from a search result, which instantly redirects you to example2.com. Both pages would get stored in your history, so pressing "back" from example2.com would send you to example1.com, which would redirect you again and add more troublesome history entries. This doesn't make it impossible to leave (quickly hitting the back button twice might work), but it does make it harder to leave, which is the end goal.

    To stop this kind of history manipulation, bad history entries will soon get a "skippable" flag, which means the back button will ignore them when it navigates through the history order. One commit says Google still needs to come up with some kind of "pruning logic" to declare a website as skippable, but that could probably be done with something like a timestamp. You spent zero seconds on that redirect page, so that's probably not a good history entry.

    This feature has been tossed around as a Chromium bug report for two years, but, with commits actively happening now, we might see it pop up in a nightly Chrome Canary release soon.

  2. The Following 2 Users Say Thank You to Teh One Who Knocks For This Useful Post:

    Godfather (12-20-2018), RBP (12-19-2018)

  3. #2
    Shelter Dweller lost in melb.'s Avatar
    Join Date
    Feb 2011
    Location
    Down Under
    Posts
    23,762
    vCash
    7596
    Mentioned
    18 Post(s)
    Thanks
    18,671
    Thanked 7,553 Times in 5,206 Posts

  4. The Following User Says Thank You to lost in melb. For This Useful Post:

    RBP (12-19-2018)

  5. #3
    Shelter Dweller PorkChopSandwiches's Avatar
    Join Date
    Jan 2011
    Posts
    77,135
    vCash
    5000
    Mentioned
    15 Post(s)
    Thanks
    47,197
    Thanked 29,254 Times in 16,488 Posts






  6. #4
    Basement Dweller Godfather's Avatar
    Join Date
    Jan 2011
    Location
    Vancouver
    Posts
    16,820
    vCash
    13129
    Mentioned
    28 Post(s)
    Thanks
    4,305
    Thanked 6,770 Times in 4,009 Posts
    That's awesome. This has been a peeve of everyone's since almost the beginning of the internet


    Chrome still doesn't have my love though because it's a CPU/Memory hog, and I need to multitask.

  7. The Following User Says Thank You to Godfather For This Useful Post:

    Hal-9000 (01-03-2019)

  8. #5
    transracial Hal-9000's Avatar
    Join Date
    Jan 2011
    Location
    On the Discovery
    Posts
    92,141
    vCash
    1000
    Mentioned
    1 Post(s)
    Thanks
    5,799
    Thanked 11,829 Times in 8,168 Posts
    I just right click on the back/forward buttons and select where I was from the list.

    Getting stuck like that is the same as when a site puts up a notice about my adlblocker and won't let me continue until I've whitelisted it.

    Fine, I go to other sites

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •