> the original idea was to not allow them to mistype the first one, then paste the typo in the second field. correct. the other analysis here is wrong. we see

> the original idea was to not allow them to mistype the first one, then paste the typo in the second field. correct. the other analysis here is wrong. we see similar for payments where user is not allowed to paste in ACH info. but this isn’t exactly about user error per se. this is about support cost for bad entries. if the user types a wrong password during registration the recovery of such is very hard. the common user (even of a product like fusion) is VERY unsophisticated and will have severe problems recovering. the more advanced user will have plugins that disable paste disabling. the middle skill user (like in the post) will get past it on their own. so net net this is just another case of this is why we can’t have nice things. they “have to” address that bottom (skill) level of users. personally i can excuse this. the rest, not so much!