Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Date picker widgets do not solve any validation problem, because validation happens on the server side and client input is not to be trusted.


Obviously, but additionally, providing validation on the frontend can help UX a lot. Doing that can provide much quicker feedback compared to an error thrown at the user only after submitting a form, which can get especially annoying if the latter loses (some of) its values due to submission. And one solution for that problem can be using a native picker.


That is called input assistance, confusing it with validation is the source of millions of security problems.


That’s an interesting suggestion, but it is not, it’s called (client side) form validation

https://html.spec.whatwg.org/multipage/forms.html#client-sid...

I definitely see your reasoning for wishing it had a different name though.


I do understand what "client-side" validation is, but I wish it had a different name, because people think they can just validate client-side and they do not bother doing it on the server... for some reason, I do not know. It should be obvious though, right? Yet it is not.


No, it's not. And if that's what confuses one, it will not be the actual source of these problems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: