3 ms·
It’s 2016 already, how are websites still screwing up these user experiences?
- mschuster91 11y ago> When you block a character, I’m going to assume one thing: your input sanitisation and your query parameterisation sucks. Not really. This is to reduce issues with users unable to login because... 1) they might have used symbols like [, { or similar while registering on a Windows machine - and they cannot find these symbols written on a Mac keyboard 2) Umlauts - these are not available in foreign countries and no one knows the escape sequences out of memory 3) They're on the phone and cannot see the password in cleartext (and thus cannot spot input errors). Seriously, I accept that asterisk stuff on PCs where you might be connected to a projector or someone glances over your screen. But on a phone? Anyone looking over your shoulder can already see what you typed! > Delayed pop-over ads – evil personified I might accept these when I can close them with Esc like any other modal window in my OS. Kill that behaviour and you deserve to rot in hell. > EU cookie warnings – this is just plain stupid Thank the EU for this bullshit, they mandated it.
- manigandham 11y agoThe password field should allow anything because it all gets hashed to the same size string with safe characters in the end. If users choose something funky that's their problem but if they're typing like that then they'll probably do so on all of their devices. It also discourages the use of randomly generated strong passwords with password managers by having these weird rules.
- mschuster91 11y agoIt 'd be great if the password field could encode the required rules so that a password manager could automatically generate the strongest password.
- tzs 11y ago> 3) They're on the phone and cannot see the password in cleartext (and thus cannot spot input errors) Speaking of mobile users, I've been considering allowing people to enter username/password on websites I work on by either: 1. The normal method of putting the username in the username field and the password in the password field, or 2. Leaving the username field blank and putting "username password" into the password field. The idea is that if you are using a password manager that cannot directly fill out fields in your browser method #2 lets you copy/paste everything with one copy/paste operation. Method #1, the normal method, requires two copy/paste operations, which can be annoying on mobile. Anyone see any security issues with this (assume that the separator between username and password in method #2 is a character that is not allowed in usernames or passwords)? Any non-security issues?