4 ms·
>you're giving way too much credit to the knowledge of the average computer user. If they're creating a password with ß in it I'm assuming they know how to typ
by Nadya 10y ago
>you're giving way too much credit to the knowledge of the average computer user.
If they're creating a password with ß in it I'm assuming they know how to type ß, yes. I don't expect the average user to know how to type ß. :)
- detaro 10y agoAnd then they travel and use a different device with a different keyboard layout and suddenly they don't know how to type ß anymore.
- deleted 10y ago[deleted]
- pilif 10y agoAlso that ß submitted by one browser is \xc3 \x9f in one browser and \xdf in another and \xe1 in yet another. Sure - if the client behaves correctly, you'd know what it arrives as, but some browsers don't and suddenly the password 'foobar' can be used to log-in, but 'foßbar' can't. By not allowing non-ascii characters in the first place you remove a whole class of support issues.