2 ms·
I have done some digging since posting this. Chromium appears to execute some logic to decide if it should show autofill for a given field. This logic appears
by andrewstuart 8y ago
I have done some digging since posting this.
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 https://stackoverflow.com/a/49161445/627492
- Brian_K_White 8y agoThose 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!"