Google has released an updated version of the Google Chrome browser for Android, bringing a host of updates, fixes and a few new features. The build is version 46.0.2490.76 for those keeping score at home and it should be hitting the Google Play Store and your device in the next few days. While the bulk of this update is fixes and other improvements, there is an improved image loading by allowing Chrome to negotiate with the web server to provide the best image over HTTP based on the bandwidth available and the device type. Sounds geeky right? It is and it is certainly something that developers would have to include on their sites but the key is that Google is positioning Chrome to be able to handle this without any user intervention once it is enabled.
Google Chrome for Android – Free – Download Now
The list of fixes, changes and updates in this version of Google Chrome is pretty extensive. Here are the release notes from the Chromium Blog on the release:
-
As part of Chrome’s ongoing efforts to ship features from the ES2015 specification, Chrome now supports the spread operator and new.target.
-
To prevent user annoyance and conserve power, Chrome will now defer playback of autoplay videos in background tabs until the first time the tab is foregrounded.
-
Developers can now disable Chrome’s default scroll restoration behavior on history navigation when it interferes with the app’s user experience.
-
Sites can specify origins that Chrome should preconnect to in order to improve performance.
-
Sites launched from the home screen can now modify the default color of Chrome’s UI by specifying a theme color in their web manifest instead of a meta tag.
-
Sites that have been added to the homescreen can now set a background color to show while resources load.
-
Developers can now specify a URI for Chrome to report HTTP Public Key Pinning violations to, making man-in-the-middle attacks easier to find.
-
Events generated by user action can be differentiated from events generated by script using Event.isTrusted(), allowing developers to protect against fake clicks.
-
Developers can now use CSS.escape(), eliminating the need for complicated string escape code while handling user generated identifiers.
-
Modal dialogs are now blocked by default in sandboxed iframes, preventing embedded content from abusing APIs like alert.
-
Sites can now set an iframe attribute that allows sandboxed content to launch unrestricted windows.
-
As part of our continuing policy to remove powerful APIs on insecure origins, the Cache API is now restricted to HTTPS.
-
Cache.addAll() is now supported, removing the need for polyfills enabling bulk interactions with the cache.
-
The Fetch API now supports Request.redirect, allowing more control over redirects.
-
DOMExceptions can now be constructed from scripts, making polyfills easier to build for specs that require exceptions.
-
Timer-based polling is no longer necessary to use WebRTC DataChannels, making them more efficient and convenient.
-
DevTools now has better tool tips and custom network profiles.
-
Resource Timing extensions to the Performance interface are now available without prefixes.
-
The CSS intrinsic sizing values, which allow boxes to fit their contents, are no longer prefixed.