Could you elaborate a bit why this change fixes your problem?

The newly added config key is rather cryptic named, I dont know what it does...?

Why do we need this new config flag after alll?

Any form element (button, input etc.) inserted by javascript trigger chrome autofill.
I should rename config option to disableSubmitButton.
This should be a new flag becouse this options is required for 'remote' function.

as I read the comment in the source, I am wondering, why you use a form without a explicit submit button?

Any variation of form doesn't work (even from example files).

If i doesn't disable this option bydisableHiddenInput this hidden input is created.
I always use submitHandler to process data after validation andvalidator.submitButton always is true

hmm not sure this solution is a good fit.@Arkni any opinions/ideas on this?

I'm also not sure about this solution. When someone change password and doesn't confirm this to chrome when he try to login injecting any button, input etc. restore form fields. I need find way to fix this, not skip.

Why incjecting input is required when user definesubmitHandler?

There was a pending request due toremote method andstopRequest()

This can't be replaced by attribute or store in variable?

Hi@szmagli,

I can't test it right now, but could settingautocomplete to"off" (or to a random string) on the hidden input stop the browser from auto filling the other fields?

@Arkni i tried but onload aoutocomplete should be on, before i call validation i try to change to off, password field to autocolplete="new-password" but chrome ignore that.