Google released earlier today Chrome 67, the latest stable release of its web browser. According to changelogs released with Chrome 67, this version adds support for a Generic Sensors API, improves AR and VR experiences, and deprecates the HTTP-Based Public Key Pinning (HPKP) security feature.
Users can update to the latest version via their browser’s auto-update system in the “Help > About Google Chrome” section. As of today, the Chrome stable version number is v67.0.3396.62.
New Generic Sensors API
Probably the biggest change in Chrome 67 is the addition of the Generic Sensors API. As the name implies, this is an API that exposes data from device sensors to public websites.
The new API is based on the Generic Sensor W3C standard. Intel, the company whose engineers proposed the API, has a website devoted to demonstrations of the sensor APIs with sample code available for download.
This API is meant primarily for mobile use, and in its current version, websites can use Chrome’s Generic Sensors API to access data from a device’s accelerometer, gyroscope, orientation and motion sensors.
Another API that shipped with Chrome is the WebXR Device API. Developers can use this API to build virtual and augmented reality experiences on Chrome for mobile-based VR headsets like Google Daydream View and Samsung Gear VR, as well as desktop-hosted headsets like Oculus Rift, HTC Vive, and Windows Mixed Reality Headsets. API documentation is available here.
Last but not least, users of Chrome 67 can now flip a Chrome flag to enable and test Chrome’s new UI. Details on what flag you need to edit are available in our previous coverage, here.
Just like Google Chrome 66, this month’s v67 also ships with loads of security-related changes. Similar to last month, Google has continued to roll out the Strict Site Isolation feature to more users, on more platforms.
Google has been using the Strict Site Isolation feature to mitigate the effects of the Meltdown and Spectre flaws. With new Meltdown and Spectre variations revealed last week, the feature is more than welcomed, even if it wasn’t originally developed to deal with CPU bugs.
Chrome 67 is also the first Chrome version that supports the new WebAuthn passwordless authentication protocol. The protocol was formally announced last month, and Mozilla beat Google by adding WebAuthn in Firefox a few weeks back with the release of Firefox 60.
Last but not least, starting with v67, Google has dropped support from Chrome for the HTTP-Based Public Key Pinning (HPKP) standard. More on this change in our previous article on the topic from last year.
Users interested in finding out what else was included with Chrome 67 can check this blog post from the Chromium team or Chrome 67’s full changelog (slow-loading link). The release notes for Google Chrome Enterprise v67 are available here.
The security-related bugs fixed in Chrome 67 are detailed in a separate blog post, here. This month, the Chrome team fixed 34 security issues.
>> Source Link