Yup. Very frustrating as a dev. I don’t really get how they rationalize it either - having their autofill appear over and obstruct a developers autocomplete functionality is not user friendly!

I don't think "millions of end-users" want broken websites because now another developer (Google) gets to decide what's correct (instead of the web dev).

A better solution could be to just behave reasonably by default but allow the user to re-enable auto-fill with a single click.

Surely there’s a way to check if a field has some kind of programatic interaction like typeahead. Maybe check for that before taking over with autofill? I don’t know - maybe that would break spec or something - I’m not a browser developer. I just know the pain of autocomplete=“off” not working as expected.