This is meant as a tracking bug for known issues with Autofill in Chrome (supported as of Android P).
- Autofill stops working until Chrome is restarted (observable on Android Q+)
This is likely caused by this bug in Android and can be confirmed by enabling verbose Autofill logging in developer options searching the output of adb logcat for occurences of the regex chrome.*forAugmentedAutofillOnly=true.
Fix: I have filed an Android bug and a Chrome bug. Ideally, Chrome would work around this issue on all versions of Android by labelling their URL bar as important for Autofill. Fixed in Chrome 89.0.4326.0
Temporary Workaround: Tap on the URL bar, then long-tap and select "Autofill". This resets the current session to not use augmented Autofill.
Permanent Workaround: Disable the app "Device Personalization Service" from its "App Info" tab.
- Autofill popups don't show on some page loads, but do on others (observable on Android P+)
This is caused by a design incompatibility between Android's implementation of the Autofill accessibility compat mode and Chrome's accessibility backend as explained here.
Fix: I have filed a Chrome bug and a CL that fixes the underlying accessibility issue in Chromium. Fixed in Chrome 86.0.4204.0
Workaround: Implemented in #921, can be enabled from the settings via "Improve reliability in Chrome". Tap the "Tab view" button and reselect the current tab.
- Autofill stops working until Chrome is restarted (observable on Android P+)
This is caused by reaching the maximum number of allowed partitions in an Autofill session. If the URL bar is not detected as having been changed, navigating between tabs all plays out in a single Autofill session. This may not be an issue in practice since it requires 10 Autofill triggers in a row. Can be detected in the logs via the regex because session \d+ reached maximum of.
Fix: A CL that mostly works around this limitation is under review here. Fixed in Chrome 89.0.4342.0
Permanent workaround: Increase the number of partitions via e.g. adb shell settings put global autofill_max_partitions_size 100.
Temporary workaround: To get Autofill working in a tab when the maximum partition count has been reached, open the recent apps menu and return to Chrome. This will allow one more Autofill trigger.
- Autofill cannot save unmasked password if the password field is masked
As of Android O, Chrome respects the masking state of password fields when reporting their contents to Accessibility services.
Fix: Chrome should report the unmasked password at least if there is not other Accessibility service than Autofill. This is the content of a Chrome CL. Fixed in Chrome 89.0.4346.0 if no Accessbility service is enabled
- Chrome starts lagging on large pages when Autofill is enabled
When loading a large web page (e.g. basically anything on https://cs.chromium.org), Chrome becomes unresponsive for more than 10s of Autodill or an Accessibility service are enabled.
This is likely caused by a helper function that traverses the entire Accessibility tree twice on every event.
Fix: A fix is being developed in this Chromium CL. Mostly fixed in Chrome 89.0.4356.0