![]() ![]() That said, to be 100% clear I am not suggested a dependency here, email_address is broken and not suitable for what we want here.Ī rushed half measure here will just create a “break email on my site” site setting which I am not particularly keen to I well understood what Jeff is meaning, and like you, I am against what he proposes (no offence to him, disagreements happen). We could start with a dumber optional normalizer. Normalizing is less user hostile and requires no new UX. ![]() is not allowed in email addresses (new message) The banning would impact OAuth and cause login with gmail to fail for it to work correctly.Įmail address. Many people that use gmail do not know that works as their email when they always thought was their email. The simple route of ban anything that is not /a-zA-Z0-9/ works but has major usability issues, a large amount of people will not know how to sign up and we would need new error messages. Given the rarity of this complaint and the exceptional circumstances around it, I think going the simple route is preferred.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |