EDIT: Just to clarify since someone took up a example with no paste on password. We just have this function on the email-field.
EDIT: Just to clarify since someone took up a example with no paste on password. We just have this function on the email-field.
It's a lazy naive "solution" that makes my life harder for no good reason. Take effort to implement good validation and recovery:
1. Use client-side validation (HTML5 field ideally) and look up the domain part. Offer "did you mean" suggestion for typos of very popular domains.
2. As long as user is signed in allow them to change e-mail post registration (e.g. "We've sent e-mail to xxtypo@geemail.com and haven't received confirmation. [Change e-mail address]")
Arguably even worse is TalkTalk's login form, which disables pasting into the password field. So I can't just copy my password there from a locket, I have to retype it. As a result I have chosen a stupidly easy-to-break password, just so I have a chance of typing it correctly, unlike the "gr2@tGig^monE"-stype passwords I otherwise use.
EDIT: Edited my main commented due to a comment regarding password fields blocking CTRL+V
It seems like if I'm restricted by this right now (hell, I type my email in roughly 6-7 times a day, with 100% success!) what level of 'fixes' will I experience when I am inside?
https://developer.mozilla.org/en-US/docs/Mozilla/Preferences...
Here's a discussion of disabling paste on passwords and usernames:
http://stackoverflow.com/questions/4760132/improving-login-s...