Google Chrome 65 release information

Martin Brinkmann
Mar 7, 2018
Updated • Jun 14, 2018
Google Chrome
|
19

Google started the rollout of the web browser Google Chrome 65 for desktop and mobile systems earlier today.

The release post on the official Chrome Releases blog does not reveal much about changes, improvements or new features but an hour-long combing through of the official changelog revealed several interesting changes in Chrome 65.

Desktop users can load chrome://settings/help to run a manual check for updates. Chrome should pick up the new version, 65.0.3325.146, on page load. The situation is different on Android where the new release is rolled out gradually to devices.

Chrome 65

google chrome 65

One of the new features of Google Chrome 65 is a new tab-under blocking mechanism designed to prevents sites from abusing clicks on links. Google demonstrated two abuse cases in October 2017 where sites would load a URL after a link click in a new tab and change the URL of the source page to a different address at the same time.

Tab unders are used by malicious actors, spammers and also for advertising purposes. What made them interesting up until now was that Chrome's built-in popup blocker did not block them.

Chrome 65 includes another security related improvement. The browser ignores the presence of download attributes on anchor elements with cross-origin attributes to protect against cross-origin information leakage.

Chrome 65 supports the TLS 1.3 draft-23 version.

Google revealed some development-related changes back in February when it announced the upgrade of the beta channel of the browser to version 65. Google added support for the Server Timing API and CSS Paint API to the browser as well.

Other changes

  • Add chrome://flags#enable-webauthentication to enable support for PublicKeyCredentials in
    CredentialManager
  • Add chrome://flags/#ignore-previews-blacklist to "ignore decisions made by the PreviewsBlackList.
  • Add chrome://flags/#show-autofill-type-predictions to show autofill predictions.
  • Add chrome://flags/#enable-downloads-location-change to change the downloads location on Android.
  • Disable fullscreen for mixed content pages on iOS.
  • Removed compact translate UI flag.
  • The Network Panel displays previews for all HTML responses (again)

Chrome 65 is a security update for the Chrome web browser. Google fixed a total of 45 different security issues in the Chrome web browser: all security fixes are listed on the Chrome releases blog linked above.

Closing Words

It is recommended to upgrade to Chrome 65 as soon as possible as it includes important security fixes and improvements.

Now You: What's your take on the general state of Chrome and Chrome 65 in particular?

Summary
Google Chrome 65 release information
Article Name
Google Chrome 65 release information
Description
Google started the rollout of the web browser Google Chrome 65 for desktop and mobile systems earlier today.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: «

Comments

  1. Taomyn said on March 8, 2018 at 8:38 am
    Reply

    “Add chrome://enable-downloads-location-change to change the downloads location on Android.”

    Is missing “flag/#” text in link

  2. chesscanoe said on March 8, 2018 at 4:23 am
    Reply

    It’s somewhat interesting that Chrome beta x64 under Win10 x64 only updated to Version 65.0.3325.125 (Official Build) beta (64-bit) .

  3. ilev said on March 7, 2018 at 8:32 pm
    Reply

    Chrome 65 has video black screen problem with some hybrid (Intel/AMD) graphic cards :

    https://bugs.chromium.org/p/chromium/issues/detail?id=810713

  4. 11r20 said on March 7, 2018 at 7:15 pm
    Reply

    Thanks Mr Martin, You do great work.

    But I’ve wiped anything google off everything i
    own…I have no intention of feeding the beast.
    They became a minion of the devil a long time ago, and gotten even worse with their censorship and hatred of the American people.

    1. richard said on March 8, 2018 at 12:38 am
      Reply

      Why are you even here on this article? Why you opened it if you don’t care or use Chrome anymore? I think Microsoft is the anti-christ but I have better things to do than reading Windows related articles and post about how evil Microsoft is.

      1. Lol said on March 8, 2018 at 7:42 am
        Reply

        Typical google fanboy

      2. richard said on March 8, 2018 at 10:34 am
        Reply

        Typical winblows fanboy

    2. Mark said on March 7, 2018 at 10:35 pm
      Reply

      lol okay

    3. Bobby Phoenix said on March 7, 2018 at 9:03 pm
      Reply

      Best comment for me today. Thanks for the chuckles. :-)

      1. Sebas said on March 8, 2018 at 1:51 pm
        Reply

        He is right about the censorship though and not only for Americans:

        http://thehill.com/policy/technology/356966-prageru-sues-google-youtube-for-censoring-conservative-videos

        https://www.wsws.org/en/articles/2017/11/22/pers-n22.html

        Messages from the left and right side of the political spectrum.

  5. Richard Allen said on March 7, 2018 at 3:55 pm
    Reply

    The “Block tab-unders” flag has been working very well for me and I wish every browser had the same functionality and it worked as good as it does in Chrome. Annoying as hell when you have javascript disabled except for inline js and you still see redirects.

    I noticed in Chrome 65 that the Qualys client test shows TLS 1.3 working with the flag set to ‘Default’. I’ve been using the flag for a while and with each major version update the flag would get changed and had to be reset which is why I noticed. Chrome Dev also has TLS 1.3 working with the flag set to Default. In Chrome, I’m seeing Experiment 2, Draft 22 and Draft 23. What’s the difference?

    https://s14.postimg.org/olfh9v1r5/Chrome_SSL_Client_Test.png

    1. Richard Allen said on March 7, 2018 at 4:18 pm
      Reply

      Dang it, I misspoke. On a couple websites I see redirects, tab-unders with inline and 1st-party js enabled, but with 3rd-party js and iframes disabled and the uBO pop-up blocker is ineffective.

  6. Vulkann said on March 7, 2018 at 2:16 pm
    Reply

    Chrome 65 seems to have at least in my case a slight lag in the spinning circle animation in the tab when the page is loading, same when you open a new tab you can clearly see that the tab opening animation isn’t as smooth as it was in the previous version v64. Has anyone else noticed something similar?

    1. Tom said on March 9, 2018 at 7:38 pm
      Reply

      I also experienced a slight graphical lag when opening new tabs (and while these new tabs are loading). I fixed this issue by using CCleaner. I selected every check box under Applications/Chrome. After cleaning the lag was gone and everything was back to normal.

    2. Tom said on March 9, 2018 at 7:29 pm
      Reply

      I also experienced a slight graphical lag when opening new tabs (and while these new tabs are loading). I fixed this issue by using CCleaner. I selected every check box under Applications/Chrome. After cleaning the lag was gone.

    3. Boo Berry said on March 8, 2018 at 11:21 am
      Reply

      There’s also a lag with opening and closing tabs too it seems. Anyone file a bug about it yet?

    4. sam said on March 8, 2018 at 7:17 am
      Reply

      > lag in the spinning circle animation…

      Same here. Using Chrome x64. Intel cpu & Amd graphics if that helps. Win 7 x64.

    5. JC said on March 8, 2018 at 12:21 am
      Reply

      Yup, I noticed the same thing. Sometimes there’s an awful lag in the tab opening animation.

    6. Richard Allen said on March 7, 2018 at 3:33 pm
      Reply

      No lag but I think if the frame rate of the animation was bumped up it would look better. Right now, for me, it might look better in Chrome Dev, hard to say. ;)

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.