Is normalizeAttributeValues a safe minification strategy?

[awerlang]

Since it cannot know future valid enumerated values for an attribute, and may not be practical even to keep it up-to-date, should it be deemed safe?
It has shown to break user code: parcel-bundler/parcel#8828

Ref: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fe-autocomplete

[SukkaW]

Since it cannot know future valid enumerated values for an attribute, and may not be practical even to keep it up-to-date, should it be deemed safe?

Normalizing the value is essential for further modification. And if something is not up to date, you can always submit a PR to fix it.

[awerlang]

I notice a PR to remove autocomplete from the module, that's one case.

I'm saying in general this feature can lead to observable change, wouldn't the max preset a better preset for it?

safe — a default preset for minifying a regular HTML in a safe way (without breaking anything)
ampSafe - same as safe preset but for AMP pages
max - maximal minification (might break some pages)

Moving it the the max preset still enables further minification, while keeping the safe preset honoring its description.