Parsley.js: never write a single JavaScript line to validate your forms

Re:Parsley.js: never write a single JavaScript line to valid... by dinkumthinkum on Sunday January 20, 2013 @05:23PM (#5088511)

1. I agree, of course. Surely, everyone knows this right?

2. True, but you have to do something. :) What exactly is wrong with [email protected]? That could be valid domain at some point, right? You could filter those out but it's almost a preference sort of question. Does anyone think it would make sense to have "warning" level of validation for email addresses and let the user decide on these sort of examples? Just throwing it out there.

[ Parent | on HN ]

Re:Parsley.js: never write a single JavaScript line to valid... by jiggy2011 on Sunday January 20, 2013 @08:25PM (#5089248)

To fix that, you can do a DNS lookup and check the domain has a valid MX record.

[ Parent | on HN ]

Re:Parsley.js: never write a single JavaScript line to valid... by robomartin on Sunday January 20, 2013 @09:21PM (#5089467)

Just be careful when you do this. If you don't use an absolute FQDN you can trigger severe delay in getting a response from the resolver. It can take twenty or thirty seconds (or more) to get a response.

[ Parent | on HN ]

Re:Parsley.js: never write a single JavaScript line to valid... by guillaumepotier on Monday January 21, 2013 @01:59AM (#5090321)

At some point if you want to be absolutely sure, you'll have to send a validation link / email and not doing it frontend in JavaScript ;)

[ Parent | on HN ]

Re:Parsley.js: never write a single JavaScript line to valid... by iambibhas on Monday January 21, 2013 @04:26AM (#5090670)

HTTP calls for client side validation? That's a great idea!

[ Parent | on HN ]

Re:Parsley.js: never write a single JavaScript line to valid... by optymizer on Monday January 21, 2013 @10:46AM (#5091932)

"This username has already been taken."

[ Parent | on HN ]