Fix annoying areYouSure confirm caused by Chrome auto filling (failed trial)

[wxiaoguang]

Closes #16861

Chrome always auto fills some inputs, and triggers areYouSure confirm when leaving, autocomplete=off doesn't help at all (see the screenshots in the issue above, even if there is autocomplete=off, Chrome still auto fills)

So we can just wait for a few seconds, then the changes of the inputs are sure to be caused by real users.

Tested and it works as expected.

[lafriks]

Shouldn't something like 1 second shouldn't be enough? 3 seconds seems a bit too much imho

[wxiaoguang]

I think it doesn't differ much for real users. 3 second is safer to make Chrome do its private operations.

No user would complete a complex form in 3 seconds. If he/she can complete a form in 3 seconds, then he/she won't worry about the lost of the content because the content can be re-filled in another 3 seconds very soon. 😂

[lafriks]

but if you edit form it could be also simple checkbox that needs to be changed

[wxiaoguang]

OK, I will try more, and I find a new problem about auto filling ...

[silverwind]

Suggested change

	// Chrome always auto fills some inputs, and triggers `areYouSure` confirm when leaving, `autocomplete=off` doesn't help at all.
	// so we can just wait for a few seconds, then the changes of the inputs are sure to be caused by real users.
	// Prevent confirm dialog from triggering on browser auto-fill

Autofill is not Chrome-specific and I think this comment is descriptive enough

[silverwind]

Suggested change

	}, 1000);
	}, 2000);

Maybe a better compromise. I for example use BitWarden to autofill and it certainly has a bit of delay to it where 1s might not suffice. If we could somehow detect autofill, that would be an even better option but I'm not sure if it's possible.

[silverwind]

Autofill detection might be possible by monitoring for an input event which I assume would only fire on actual user input, but it needs to be tested. I think it might be possible to only register the areYouSure handler after the form has received its first input event.

[wxiaoguang]

I meet a new problem. Chrome is really annoying. I am thinking about a totally new solution ....

    // Chrome always auto-fills some inputs, and triggers `areYouSure` confirm when leaving, `autocomplete=off` doesn't help at all.
    // When a page is just loaded, JavaScript can not read auto-filled fields before a user interaction occurs,
    // then the problem becomes:
    //   1) A page gets loaded, users can saw fake auto-filled input values, JavaScript can only get empty strings for the auto-filled inputs.
    //   2) When user clicks or inputs, Chrome auto-fills real input values. Then JavaScript can read real values.

[silverwind]

Maybe https://github.com/matteobad/detect-autofill is useful, but it looks to be quite a hack.

[wxiaoguang]

After some investigation, the solutions all seem very hacky, so I think we had better close this PR and to see whether there are better solutions.