Chrome 59 was just released, which means Chrome 60 has graduated to beta status. This version includes a few interface changes, like a new context menu and file picker, as well as a new search widget. The Vibration API also has some new limitations to combat malware ads. Let’s take a look.
New search widget
We previously covered Chrome’s new search widget, which was developed as a result of an anti-trust lawsuit Russia. Russian search company Yandex claimed that Google violated local competition rules, and the settlement required Google to develop a search widget that could change between search engines.
At some point, this will replace the normal Google search widget for Android phones sold in Russia. It uses whatever search engine you have set in Chrome, and starting with version 57, Chrome supports almost any search engine you could want to use. It doesn’t appear to have changed since we covered it in Chrome Dev 60.
No more vibrating ads
You’ve probably seen those fake full-screen malware ads before – the ones that vibrate your phone. This is possible thanks to the Vibration API introduced a few years ago. I’m sure someone thought that web games would be pretty cool with if they could vibrate your phone, but I’ve only ever seen it used by malicious advertisements.
Starting with Chrome 60, pages will no longer be able to vibrate your device unless you tap on the page first. I still think the Vibration API should be removed entirely, or at least have to ask the user permission first (like camera access), but this is a step in the right direction.
In a similar move, the beforeunload JavasScript function will only work if you have tapped on the page. This is also commonly used by malicious advertisements, to show an alert as you try to close the window/tab.
If you’re not aware, the ‘context menu’ is the