After a short rollout delay, Chrome 79 is now widely available on desktop and mobile platforms. That means Chrome 80 has moved up to the beta channel, and while there are a few new features, there are far more removed features. Let’s dive right in!
It seems like spring cleaning is coming early for Chrome. Several feature experiments that have shown up over the past few months have been completely removed, possibly marking an end to much-anticipated functionality.
First is #overscroll-history-navigation, which we first covered in March of this year. It added the ability to navigate back and forward using horizontal swipes. Perhaps with the advent of full-screen gesture navigation in Android 10, Google deemed this feature unnecessary.
The #overscroll-history-navigation feature
Similarly, the horizontal tab switcher that first appeared over a year ago is gone. When the #enable-horizontal-tab-switcher flag was turned on, Chrome tabs were displayed horizontally instead of in a vertical stack.
Left: Regular tab switcher; Right: Horizontal tab switcher
The #enable-ntp-remote-suggestions flag has also been removed, so it’s no longer possible to completely remove article suggestions on the New Tab Page. They can still be hidden by tapping ‘Hide’ in the ‘Articles for you’ section of the page, but a button for turning them back on remains.
Both flags for Reader Mode are also missing (#reader-mode-heuristics and #enable-reader-mode-in-cct), which seems to mark the end of the long-awaited feature. It was a bit surprising in the first place that Google would add a mode that removed advertisements from web pages, so its removal probably won’t shock anyone.
Content Indexing API
Chrome already allows sites to save copies of pages, images, scripts, and other files to your phone — this is what makes offline Progressive Web Apps work. However, there is no browser-level interface for checking what exactly is downloaded locally, so it’s up to the web site to explain what is and isn’t available offline.
Google is attempting to solve this problem with the Content Indexing API, available as an Origin Trial (opt-in beta) in Chrome 80. Web apps can now add or remove content in the ‘Articles for you’ section of the Downloads page. This is opt-in functionality, so it won’t list all files stored by web apps on your device. You’ll still have to open the storage settings for the Chrome app to get the full picture.
In a blog post, Google said, “Chrome is [also] running experiments to proactively recommend this content when it detects that a user is offline.” As such, this functionality might become more apparent to users in future releases.
More HTTPS changes
Google’s fight against unencrypted HTTP pages wages on. Most recently, Chrome has been slowly pulling back on support for “mixed content,” where unsecured HTTP content is embedded on HTTPS pages. The browser already warns you when mixed content is detected, and now Chrome will try to fix the issue whenever possible.
A new feature in Chrome 80, called Autoupgrade Mixed Content, will attempt to replace the “http://” in any URLs it loads with “https://,” similar to what extensions like HTTPS Everywhere have offered for years. For now, only video and audio links will be upgraded, but the Chrome team hopes to expand this to more types of content in the future.
Many years ago, the File Transfer Protocol (FTP) was a popular way to host files online. However, it was never designed to be a secure protocol, and suffers from countless vulnerabilities. Now that it has largely fallen out of use, Chrome will soon drop all support for FTP connections.
This has been a long time coming, as Chrome 59 started blocking pages from embedding content from FTP servers, and Chrome 72 started forcing all FTP links to be downloaded instead of viewed in-browser. According to the Chrome dev team, FTP usage is now so low that it’s safe to remove all support:
The current FTP implementation in Google Chrome has no support for encrypted connections (FTPS), nor proxies. Usage of FTP in the browser is sufficiently low that it is no longer viable to invest in improving the existing FTP client. We would like to deprecate and remove this remaining functionality rather than maintain an insecure FTP implementation.
FTP support is now deprecated in Chrome 80, which means it still works, but it will start to become disabled by default for some users (via the #enable-ftp flag). Google plans to remove all FTP code and support in Chrome 82. There’s no message when visiting an FTP server about it being insecure or unsupported, you just get a blank page.
Chrome with FTP support enabled (left) and disabled (right)
If you still need to access files on an FTP server, there are plenty of separate applications designed for that very purpose — my favorite is Cyberduck.
As always, Chrome 80 includes changes for both users and developers. Here are some smaller changes in this update:
- Support for Custom Elements V0, Shadow DOM v0, and WebVR v1.1 have been removed entirely.
- Cookies are now marked as ‘SameSite=Lax’ by default, to prevent cross-site cookie reading unless the site developers specifically opt-in.
- Synchronous network requests sent while closing tabs are now blocked.
- Popups created when a tab is being closed are now blocked.
- Support for HTML Imports have been completely removed, because ES Modules do the same thing and work with other browsers.
- Sites can now check what decoding abilities your device has, so streaming music and videos won’t use a decryption format that is overly battery-intensive.
- A new ‘Periodic Background Sync’ feature allows sites to schedule push notifications for the future without setting up an external server.
- The new Serial API allows sites to communicate with hardware devices over a physical or virtual serial port, once given permission.
- SVGs can now be used as favicons.
The APK is signed by Google and upgrades your existing app. The cryptographic signature guarantees that the file is safe to install and was not tampered with in any way. Rather than wait for Google to push this download to your devices, which can take days, download and install it just like any other APK.
Note: Most versions of the Chrome APK use app bundles, which APKMirror doesn’t support yet. As a result, only a few variants are available for download.