[antoinevg]

...which really makes it worse:

1. Our programming language has an attribute called "autocomplete" with two possible values: "on" and "off"

2. We will now (without consultation or announcement) simply start ignoring one of those values when you specify it. (and certainly not document the new behaviour!)

3. Here, I made you a convoluted (and undocumented!) workaround for getting the original behaviour of the attribute back.

I'm not sure which horse these FAANG kids who excel at programming challenges rode in on, but this attitude is RIFE in their product SDK's and API's.

Dijkstra must be spinning in his grave.

[tgv]

All that based on an increase in page submissions. Is that the goal of auto-complete?

The research behind the number (25%) is highly dubious, because the video cited as the source doesn't tell how it was done. At all. Ironically, it follows a section on how MDN is documenting the standards, and how that "contribute(s) a lot".

[mnoorenberghe]

There are more than 20 different valid field name tokens in the spec, not just “on” and “off”[1]. If web developers actually used the other values correctly then user agents wouldn’t need to use heuristics to figure out the correct data to autofill.

[1] https://html.spec.whatwg.org/multipage/form-control-infrastr...

[mehrdadn]

I'm reminded of an earlier comment: https://news.ycombinator.com/item?id=21083277