For years, autoplaying video and audio on the web has been a constant source of frustration for users. Restrictions on autoplaying content have been in mobile browsers for years, partially due to the processing limitations of early smartphones, and partially to conserve mobile data usage. With the release of Chrome 66 late last month, Google introduced new autoplay restrictions on both mobile and desktop Chrome.

Google Chrome 66 came out a few days ago, with your usual list of new APIs and user improvements. However, one major new feature flew under the radar. This is the first stable Chrome release with experimental support for Valve's OpenVR API, allowing VR content to be viewed on all popular headsets. This includes the HTC Vive, Oculus Rift, and Windows Mixed Reality headsets.

It has been about a month since Chrome 65 was released, so it's time for another update. Google's browser has now moved up to version 66 - cue the 'Order 66' jokes. This update has plenty of changes, including two major interface revamps hidden behind flags.

Chrome 65 came out last week, and included Google's new ad-blocker and a few other security features. Chrome 66 has now graduated to the beta channel, and has several major experimental features. There's a new 'Modern Design' interface, partially based on the ill-fated Chrome Home UI, as well as updates to the media player and a new Clipboard API.

For over a year now, Google has been working on an overhaul of Chrome's interface on Android, called 'Chrome Home.' It moved the address bar to the bottom of the screen, and pulling up on the address bar would reveal an updated New Tab Page. Despite it being mostly ready for release, Google canned it earlier this month for reasons unknown.

If you frequently use your phone or tablet to browse the web, you've probably noticed how some websites randomly redirect you to a fake virus warning or other similar page. This is due to malicious ads breaking out of their frame, and forcing a redirect of the parent page to wherever they want. These harmful ads have infiltrated virtually every ad network, including Google AdSense/AdX.

Google's solution to this problem is a blocker for redirecting ads, which was announced in November of last year (this is separate from the general ad blocker that will arrive later this month). If an ad tried to hijack the parent page, Chrome would block it and tell the user what page it was trying to get to.