Earlier today, Google formally announced a feature that would keep rogue advertisements from taking over the browser and redirecting you to another page. We've been battling these ads ourselves (as documented here, here, here, and so on), as they have often infiltrated even 'safe' ad networks like Google AdSense.
The company said the feature would go live in Chrome 64, which is currently in the Canary and Dev channels, and not expected to be completed until January 2018. Surprisingly, the feature is already built into Chrome (even the stable version), you just have to turn it on. Read More
Version 62 of the Chrome browser was released a week ago, and Chrome OS updates usually follow closely behind. Chrome OS 62 has started rolling out to Chromebooks, featuring improvements to the file manager, a new design for Chrome OS notifications, fixes for the KRACK vulnerability, and more. Read More
It has been about a month and a half since the last Chrome release, but good things come to those who wait, right? Chrome 62 includes yet another redesign hidden behind a flag, some new APIs developers can use, and several smaller tweaks. So without further ado, let's get into it. Read More
Chrome 61 was a huge update. Not only did the long-awaited Chrome Home UI (the bottom URL bar layout) finally start rolling out, but it also improved the Google Translate bar and file picker. Chrome 62 isn't quite the overhaul that 61 was, but it already has improvements to the round Chrome Home UI and enables several new APIs and features. Read More
The experimental 'Chrome Home' interface first appeared in October of last year, and at the time, only moved Chrome's address bar to the bottom of the screen. Google has continued to work on it since then, like adding a revamped New Tab page with a bottom tab bar. A new flag has appeared in Chrome Canary, that further changes the Chrome Home interface by making everything round. In other words, there's a new experiment for the experimental UI. Read More
Google has been planning to mark all HTTP sites as non-secure in Chrome for a while now, but the company is taking baby steps to ensure users (and owners of HTTP-only sites) don't freak out. Chrome already identifies HTTP sites with password or credit card fields as "Not Secure" in the address bar, and Chrome 62 will expand that to any HTTP site with any data entry fields. Read More