...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.