Today Google updated the stable version of its Chrome browser to version 36.0.1985.122 on Windows, OS X, and Linux. The update contains a couple of visual changes as well as some under the hood improvements. Below is the full list of changes provided by Google.

  • Rich Notifications Improvements 
  • An Updated Incognito / Guest NTP design
  • The addition of a Browser crash recovery bubble
  • Chrome App Launcher for Linux
  • Lots of under the hood changes for stability and performance

The first two listed changes are mainly visual. The changes to the incognito tab landing page update the design of the disclaimer about incognito mode to better fit in with Google's new Material Design principles. Below we have the old landing page text on the top and the new design on the bottom. As you can see, the new design employs a greater use of white backgrounds with a shadow underneath the card.

This release also brings the Chrome App Launcher to Linux, having previously been a feature only included with Chrome for Windows and OS X. The remaining browser changes are mainly under the hood to improve stability and performance. Upon updating my copy of Chrome for Windows to version 36 my Adblock Plus addon was unable to restore my custom website filters and so Adblock Plus users with custom filter lists may want to take note of any customizations they have made prior to updating. In addition to the changes listed in Google's changelog, the update includes fixes for 26 security issues. More information about these and other changes to Chrome can be found on the Google Chrome blog below.

Update: Google is now rolling out the same 36.0.1985.122 update to Chrome for Android. The specific changelog for that update is listed below. In addition to these changes, the update contains some security fixes specific to the Android version of Chrome.

  • Improved text rendering on non-mobile optimized sites.
  • Doodles return to the new tab page.
  • Lots of bug fixes and performance improvements! 

Source: Google Chrome Blog

POST A COMMENT

37 Comments

View All Comments

  • SirPerro - Thursday, July 17, 2014 - link

    So you're saying that the number of XP computers is lower than the number of HiDPI windows displays.

    I serously struggle to find a Windows HiDPI display so let me doubt that.
    Reply
  • JarredWalton - Thursday, July 17, 2014 - link

    How many High DPI displays are used with XP, though? Um, probably none, unless you count old 30" desktop displays which are only moderately "high DPI". Reply
  • SirPerro - Thursday, July 17, 2014 - link

    Because there's really a big number of users there with HiDPI displays Reply
  • johnygl - Thursday, July 17, 2014 - link

    Yes Chrome supports HiDpi displays. How to enable it was mentioned on annandtech, here is link http://www.anandtech.com/show/7939/scaling-windows... Reply
  • Brett Howse - Thursday, July 17, 2014 - link

    In one of the builds after I wrote that article, Google broke support for High DPI and the workaround that partially worked before no longer worked.

    It's too bad it's still only fixed in a dev build of the product. Hopefully it actually is working this time.
    Reply
  • nefftd - Wednesday, July 16, 2014 - link

    Another good change that isn't listed here: when an extension changes the New Tab page, Chrome will now alert you of the change and ask if you would like to keep the changes, or revert to the default New Tab page.

    This is an excellent change to combat the increasing amount of adware that hijacks your browser's default search and New Tab page to point to their own ad-laden search page.

    I was delighted to open Chrome today and see that it had detected the Humble New Tab Page extension doing this, and alerted me. A very elegant solution to the adware problem, as it maintains the user's capability to customize.
    Reply
  • alyarb - Wednesday, July 16, 2014 - link

    How long til 37? 37 is the first one to finally render web fonts correctly. Reply
  • Alexvrb - Wednesday, July 16, 2014 - link

    I wonder if they'll skip version 666? I guess we'll have to wait a few months to find out. Reply
  • polygon_21 - Wednesday, July 16, 2014 - link

    Hope they fix the system clock tick rate issue soon...
    https://code.google.com/p/chromium/issues/detail?i...
    Reply
  • pixelstuff - Wednesday, July 16, 2014 - link

    Does anyone know the average time between the Chrome browser and matching ChromeOS versions are? Reply

Log in

Don't have an account? Sign up now