renato
June 30, 2021, 7:35pm
1
Related to New post/reply sometimes tries to autocomplete my address on Chrome .
I’m using Chrome 91.0.4472.120 on Android 11 and it gives suggestions on some fields that clutter the UI, the topic title being the most common but it also happens on the category and tag filter fields:
As a user I can long press and remove the suggestion, but most people on my community aren’t very tech savvy and I’d like to avoid this confusing behavior, any suggestions?
Thanks.
2 Likes
sam
July 1, 2021, 1:51am
2
Yikes… I am seeing autocomplete="discourse" here.
You can see the history here: FIX: use autocomplete="discourse" to disable Chrome address autofill - discourse - Discourse Reviews
According to Stack Overflow something may have changed in Chrome recently.
html, google-chrome
https://bugs.chromium.org/p/chromium/issues/detail?id=914451
The last comment on that topic is not filling me with too much promise.
@Falco any chance you can test on latest Chrome / Android to see if =off is now respected more than =discourse?
5 Likes
Yes, this came up again recently, and the only solution is …
And I see multiple SO reports that the type="search" autocomplete="off" combination works.
1 Like
Falco
February 25, 2022, 7:16pm
5
This was fixed by @pmusaraj
discourse:main ← discourse:fix-autocomplete-off-composer-title
opened 08:48AM - 01 Feb 22 UTC
We've historically used `autocomplete="discourse"` (and other variations) to cir… cumvent a stubborn Chrome issue where `autocomplete="off"` wasn't respected. But the circumvention does not work anymore either, and there are reports that for most cases, the standard has better support in Chrome. See for example https://stackoverflow.com/questions/57367813/2019-chrome-76-approach-to-autocomplete-off/57810447#57810447
We are slowly trying things in a few places, and if it works, we will be using `autocomplete="off"` across the board.
4 Likes
