This has turned into a sad chicken-race between Google and developers, with lots of innovative workarounds on Stackoverflow.

Their tactic of overruling web developers doesn't work, it only make things more complicated for everyone, since many of the workarounds have other negative side-effects.

https://stackoverflow.com/questions/12374442/chrome-ignores-...

    ## Example 1

    For a reliable workaround, you can add this code to your layout page:

    <div style="display: none;">
     <input type="text" id="PreventChromeAutocomplete" 
      name="PreventChromeAutocomplete" autocomplete="address-level4" />
    </div>

    Chrome respects autocomplete=off only when there is at least 
    one other input element in the form with any other autocomplete value.



    ## Example 2

    Simply make your input readonly, and on focus, remove it. This is a very 
    simple approach and browsers will not populate readonly inputs. 
    Therefore, this method is accepted and will never be overwritten by 
    future browser updates.

    <input type="text" onfocus="this.removeAttribute('readonly');" readonly />

    Style your input accordingly so that it does not look like a readonly input.


    ## Example 3

    Tell Chrome that this is a new password input and it won't provide 
    old ones as autocomplete suggestions:
    <input type="password" name="password" autocomplete="new-password">