Autocomplete on forms does not deactivate with false as it’s a nonstandard value. See what happens in browsers when it’s added. If it works anyway let it through otherwise treat it like off.
Look at form component, textinput and textarea.
Rather than treating a non-standard autocomplete value as "off" form control shortcode will instead alert the user of the error and attempt[^1] to fail the build until it’s corrected. In the case of a partial no error will be presented and the invalid value quietly scrubbed from the output.
[^1]: Tested in Hugo 0.46 doesn’t fail the build on errorf as stated in the docs but that’s okay because it still outputs to stdout and the big red alert ought to be reasonably obvious something’s not quite right.
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?