What is Chrome 67?
Following the release of Chrome 67 yesterday i.e. 29th of May 2018 has entered the beta channel beginning with Windows, Mac, and Linux, Google is progressing out the newest version of Chrome today. Chrome 67 which has arrived into the beta channel. A typically developer-focused release, it permits testing of the new WebXR Device API, while web applications can now access numerous device sensors. Also, there are a handful of user-facing variations on Android and Chrome OS. Chrome 67 has announced a number of features and APIs that developers can yield benefit of for virtual reality experiences and apps. In the meantime, there are the desultory bug fixes and security patches.
Chrome 67 version initiates testing the new WebXR Device API as the portion of Google’s push into a web-based virtual reality that permits for unified, platform-agnostic experiences. And adds support for a Generic Sensors API, improves AR and VR experiences, and deplores the HTTP-Based Public Key Pinning (HPKP) security feature. It contains mobile devices, portable VR headsets like desktop-connected and Daydream ones like HTC Vive, Oculus Rift, and Windows Mixed Reality Headsets.
As of now, only two features are absolutely confirmed to be making their way to the public upon the Chrome 67 full public release, both of which are used upon below.
Since Chrome 63, site isolation has always been an “under progress” feature, but it appears as though it will finally be permitted on this coming build. Site isolation mainly gives each website that is visited its specific process within Chrome’s sub-process tree, thus substituting the old tab-based system that has been used all this time. This means that security is certainly increased for the forthcoming version, however along with it will come increased RAM usage no doubt.
Web-Based VR Focus
One of the stand-out announcement points for Chrome 67 is predictable to be the foundations for web-based mobile experiences, permitting the browser to better use VR and AR APIs under the new WebXR outline. Fundamentally, this will allow for much-improved experiences for VR/AR content, allowing for developers of such content to shove the software for mobile browsers further.
This will probably include an additional focus on AR as well, as the browser is said to set the foundations of the WebXR framework which hosts APIs for both VR and AR content. To enhance to this, Google is hustling the new Generic Sensor API into Chrome 67, which will possibly help deliver better VR/AR experiences, among other applications.
Significant changes in Chrome 67
- A number of fixes, enhancements, and improvements.
- Progressive Web Apps are coming to the desktop
- BigInt’s make dealing with big integers way more easier.
- Credential Management API delivers a framework for making, retrieving and storing credentials.
- The generic sensor API makes it trouble-free to get access to device sensors like the accelerometer, gyroscope and more.
- The Web Authentication API enhances a third credential type, PublicKeyCredential, which allows browsers to authenticate a user with a private/public key pair generated by an authenticator.
- Better handling of boarding passes, movie tickets, etc. in Wallet
- Enhanced support for external keyboards
- Updated app selection UI when you tap on an email link
- Upgraded issue reporting: now you can draw on screenshots you are sending with feedback reports to unknown private data.
Recommended For You-