[jobead]

If you want to "turn it's features on and off", then why does the Chromium team's stance of "extensions are the standard way to enable custom behavior"[0] not apply here???

This is a classic unfortunate case of using data from the masses to drive a bad design choice because it increases "usage" along an arbitrary axis.

[0] https://news.ycombinator.com/item?id=11729287

[comex]

In the phrase you quoted, "custom" means "different from the default". It's about a choice between building customization into the browser (in the form of preferences) and relying on extensions to provide it. And it does apply here: there is no preference to honor autocomplete=off. If you want your Chrome instance to do so... find an extension.

(Though, since my quick search of the Chrome Web Store found a lot of [presumably no longer necessary] extensions to disable autocomplete=off but none to do the opposite, you might have to write it yourself. It should suffice to change "off" to an unrecognized string, as mentioned in the last comment on the issue report.)

[tracker1]

Given the autocomplete detail tokens[1] - my first thought was

    autocomplete="section-disabled disabled"

Or something similar.

[1] https://html.spec.whatwg.org/multipage/forms.html#autofill-d...

[forgottenpass]

The Chromium team's stance of "extensions [...]" is better understood as: "get the fuck off my lawn."