Feature detect best event to use on password fields

[peterwilsoncc]

Following #33385 the user profile JavaScript uses keyup events to update the password strength meter and keep the password fields in sync.

Not all input methods update fire the keyup event so we use feature detection to detect the optimal event, I propose:

• input
• keyup
• change

The optimal event to use is subjective and up for discussion.

[peterwilsoncc]

First pass in 33398.1.diff​, went with input for preference, keyup as fallback. change as third fallback not needed, it has ​less support than keyup

[peterwilsoncc]

Related #33601

[adamsilverstein]

@petewilsoncc:

This looks great, I like your approach for detecting and using the correct method. I tested your patch and verified that it works and also that it resolves #33601.

33398.diff​ (sorry for mis-naming):

• Refresh against trunk
• Doc block cleanup, use @link for ticket reference, slight language change
• Remove some extraneous newlines

[adamsilverstein]

33398.2.diff​:

• Remove @link as per chat with @DrewAPicture

[samuelsidler]

Let's consider this for 4.3.1 since it appears to be the best way to fix #33601.

[ocean90]

#33601 was marked as a duplicate.

[ocean90]

In 34060:

Passwords: Refresh password fields when content is pasted into fields.

Use feature detection to determine whether password inputs should use the keyup or input event.

Props peterwilsoncc, adamsilverstein.
Fixes #33398.

[ocean90]

In 34078:

Passwords: Refresh password fields when content is pasted into fields.

Use feature detection to determine whether password inputs should use the keyup or input event.

Merge of [34060] to the 4.3 branch.

Props peterwilsoncc, adamsilverstein.
Fixes #33398.