Chrome 59 brings security fixes, Material Design Settings
Google released Google Chrome 59 on June 5, 2017 to the Stable channel on all supported operating systems including Windows, Linux and Mac OS X.
The new version of Google Chrome ships with 30 security fixes, Settings updated to Material Design, new Developer Tools features, full screenshot capture, and under-the-hood improvements.
The official release announcement is -- as usual -- not very forthcoming in regards to the changes of the release. Google highlights the security fixes and Material Design settings, but that is about it. The company states however that blog posts about new features will be published on the official Chrome and Chromium blog, but that has not happened yet.
Google rolls out Chrome over a period of time. I never understood why the company does that, as Chrome releases usually include security fixes that all user systems benefit from.
Google Chrome 59
You can -- and should -- run a manual update check in the following way to have the new Chrome 59 version picked up right away on your devices:
- Load chrome://settings/help. Chrome lists the current version of the browser on the page.
- The browser runs a check for updates, and will download and install any new version that is returned.
If the check does not work for whatever reason, head over to the official Chrome for Desktop site instead to download Chrome 59 this way.
Chrome 59: what is new
The change that most Chrome 59 Stable users will notice is that Google switched the design of the browser's Settings page to Material Design. Google started to push Material Design changes to Chrome as early as 2015, and has yet to complete the process.
You may notice two major changes after the upgrade to Chrome 59:
- The Settings structure may have changed with Appearance settings moved to the top, and the "on startup" setting moved to the bottom.
- The Material Design version of the Chrome settings uses a slider and no longer checkboxes to toggle options.
Tip: Chrome 59 ships with an option to disable Material Design of the Settings page. Load chrome://flags/#enable-md-settings in the web browser, and set the flag to disabled. You need to restart Chrome afterwards to get the old Settings design back. This even restores the previous hierarchy of the Settings page. Note that Google will remove the flag eventually from Chrome.
Other changes in Chrome 59
The bulk of the changes are under the hood changes that benefit web applications and functionality, but are not directly noticeable by users.
- Headless Chrome is supported now, but in Chrome 59 only on Linux and Mac. Google promises that it will be enabled on Windows "soon" as well. It allows you to run Chrome in an automated environment that does not display a user interface or peripherals.
- Mac OS X native notifications. Notifications sent via the Notifications API or chrome.notifications are sent directly by the Mac OS X native notification system in Chrome 59.
- Service Worker navigation.preload API. Allows the web browser to preload navigation requests "while a service worker is starting up".
You can check out the full log of changes of Chrome 59 on the Google Source website.
Chrome 59 Developer Tools
Google added new features to the Developer Tools, and improved others. Here is a quick overview of what is new or changed for developers:
- Full Page Screenshots are supported in Chrome 59 now.Â To make use of the feature, toggle the Device Toolbar with Ctrl-Shift-M while the Developer Tools are open. Click on the menu icon displayed on the toolbar, and select the "Capture Full Size Screenshot" option from the context menu.
- The Block Request URL feature enables you to block the loading of resources to simulate how the web page behaves when the resource is not loaded. Right-click on any resource that gets loaded on page load and select "block request URL" from the context menu to do so.
- Step over async wait lets you "step from the first to last line with consistency" in Chrome 59.
- Unified Command Menu with the Open File Menu.
Now You: What's your take on the changes in Chrome 59?Advertisement