Re:Valid use cases for autocomplete=off
by Brian_K_White on Saturday September 29, 2018 @11:47AM
(#18101013)
Those are ways to work around a problem that was unneccesarily and artificially injected. Why tolerate that and work-around it on your dime? Why not instead tell the person creating the problem "hey, don't create this problem you jerk!"
Chromium appears to execute some logic to decide if it should show autofill for a given field. This logic appears to be analyzing text before the element that autofill is displayed on. I thought "if I know what that logic is then I can trick it into not displaying." I spent some time looking through the Chromium source code to find that logic and understand it, but I could not find it and don't have time to research it further. This seems the key though to managing this problem.
Other ways of addressing this might include using a different sort of HTML element instead of input. For example textarea or editable div.
More possible pointers to solutions are here: https://stackoverflow.com/a/49161445/627492