2 ms·
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
by tlamponi 11mo ago
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.
- padjo 11mo agoThat is called input assistance, confusing it with validation is the source of millions of security problems.
- __jonas 11mo agoThat’s an interesting suggestion, but it is not, it’s called (client side) form validation https://html.spec.whatwg.org/multipage/forms.html#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.
- johnisgood 11mo agoI 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.
- tlamponi 11mo agoNo, it's not. And if that's what confuses one, it will not be the actual source of these problems.