Suggesting that an authorized user would re-attempt the correct login?
I have only one real-world example of a site where I would do that, and it’s because I know that it behaves this way (though for that site, if I had to guess, it’s likely a bug related to poorly designed async handling rather than an explicit check like in the comic). In most cases, I would assume PW recorded incorrectly in the first place and go straight for the password reset workflow.
Not sure how representative that user behavior is, but the population is N ≥ 1.
Suggesting that an authorized user would re-attempt the correct login?
I have only one real-world example of a site where I would do that, and it’s because I know that it behaves this way (though for that site, if I had to guess, it’s likely a bug related to poorly designed async handling rather than an explicit check like in the comic). In most cases, I would assume PW recorded incorrectly in the first place and go straight for the password reset workflow.
Not sure how representative that user behavior is, but the population is N ≥ 1.
You are very confident in your ability to not make a typo.
How to make a typo when using password manager?
I tell you how. Password manager fills the input just a bit too fast so that misused react handler goes into race condition and skips last character.
You’re still typing PWs? I c&p them from Keepass.
How do you log on to your computer?