Yesterday on Reddit, members of the Google Chrome team conducted an AMA ('Ask Me Anything'). While the main focus of the AMA was about web development (it was on /r/webdev, after all), there were a few answers that both users and developers can get excited about.

Autofill API support is coming

One of Android Oreo's new features is the Autofill API, which allows password managers and similar tools to work without screen overlays and accessibility setting hacks. Naturally, users have been wondering when Chrome would support this functionality. The Chrome team is indeed working on it:

We are actively working with the Android Autofill team on this. We don’t have a target release that we can announce yet. We will probably let the user choose whether to use Chrome Autofill / password services or whether to use Autofill providers installed on Android. We don’t expect that we can offer both simultaneously.

Chrome will have a password generator

Google has been testing a password generator on desktop Chrome for a while now, but the Android and iOS apps have been left out. Thankfully, Google is on the case:

You will see in Chrome 62 that we have improved the password viewer on Android and iOS in Chrome Settings a lot. Being able to see your passwords is a prerequisite for generating passwords as there are these edge cases where two different different domains (e.g. amazon.com and amazon.de) share the same password. We are on it. Stay tuned!

WebVR is being re-worked

Back in February, Chrome for Android introduced WebVR support as an origin trial. This meant that the API was still under active development, and wasn't ready for widespread use. The current iteration is pretty powerful, even supporting controllers (like the Daydream motion controllers) and multiple VR platforms, but the Chrome team isn't quite happy with it:

Based on feedback received from web developers, hardware manufacturers, and other implementers the WebVR API has been undergoing a significant refactoring. The resulting new API is described in this explainer. The new API, which was designed through collaboration with WebVR Community group members, will be easier for developers to work with, support a wider variety of devices, enable better performance, and be should be significantly more futureproof. We’re looking forward to getting implementations into developers’ hands as soon as possible!

The comment went on to say that Google intends to remove support for the old WebVR API after the new one is completed, but the company will provide resources to developers for migrating existing content.

Extensions on Android aren't going to happen

Google has said quite a few times over the years that it doesn't intend to bring Chrome extensions to Android, but just in case you needed more confirmation, here it is:

Extensions create a tremendous number of challenges on mobile, in terms of resource usage, code complexity, interaction with other mobile features, and so forth.

If you really need extensions on mobile, Firefox is always an option. In fact, recent versions of the browser support WebExtensions, which is a new open framework based on Chrome's extension API. Speaking from personal experience, most Chrome extensions can be ported with little to no effort. So in a way, Chrome extensions are already on Android - just not on Chrome.

Chrome is being optimized for developing countries

Google has been hard at work making Chrome more usable in developing countries, where users are often on slower networks with less powerful devices. For example, Chrome's Data Saver continues to get better, with support for videos and downgrading web pages. When asked what upcoming features would make the biggest impact, the Chrome team responded with this:

We’re investing a huge amount in making the web more usable for the "next billion users" in places like India, Indonesia, and Nigeria, where users are typically on slower networks, less powerful phones, and pay for their data plans. We’re working on making Chrome smarter about rendering pages to use less data and memory, for example, automatically falling back to a "text only" rendering mode in some cases. We're also adding improved suggestions for pages to visit, especially for people who don't have a lot of previous exposure to the web.

Those improved suggestions first showed up in Chrome 54, but judging from the comments, many of our readers weren't a fan of them. If you're still annoyed by them, it's pretty easy to turn them off.

Chrome will have a Picture-in-Picture API

Google Chrome added support for Android Oreo's Picture-in-Picture mode earlier this year, but sites couldn't customize the behavior at all (besides disabling it). When asked about PiP in Chrome, the team responded with this:

We’ve actually shipped picture in picture for Android O in M58 and are looking at it for desktop (tracking bug at crbug.com/726619). Beyond that, we’re also looking into API support for picture in picture functionality (spec)

The Picture-in-Picture API is currently being discussed here. The current proposal would allow sites to add their own PiP button, and detect when PiP is enabled and disabled. As more and more browsers add support for the feature (Opera does on macOS), a standardized API will benefit everyone.

There you have it - the Chrome team's answers to some of your most burning questions. The team also answered a few more questions not related to Android, like an explanation for RAM usage and a status update on the Chrome Web Store. You can see the entire Reddit thread at the source link below.