5 ms·

This is the place where the date picker does not help the user at all. It's easier to type the, presumably memorized, date, than to look it up in the calendar n

by folmar 10mo ago

This is the place where the date picker does not help the user at all. It's easier to type the, presumably memorized, date, than to look it up in the calendar no matter how nice and handy the calendar is. Sure it does solve validation problem. Or maybe not correctly, don't ask about locales and date adjustments.

nozzlegear 10mo ago
Doesn't the browser automatically a handle locales when using the HTML5 input=date?
- folmar 10mo ago
  Even if, that does not help. When asked for a birthday I need validation of the date in country when I was born, not the country I'm in, not the locale I'm using for display and not the locale server/requesting company is in.
  - jrochkind1 10mo ago
    I am thinking about locale of how a date/time is formatted for display/input. Including language-specific month names etc.
dotancohen 10mo ago
Date picker widgets do not solve any validation problem, because validation happens on the server side and client input is not to be trusted.
- tlamponi 10mo 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 10mo ago
    That is called input assistance, confusing it with validation is the source of millions of security problems.
    - __jonas 10mo ago
      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-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 10mo ago
        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.
    - tlamponi 10mo ago
      No, it's not. And if that's what confuses one, it will not be the actual source of these problems.

by folmar 10mo ago

nozzlegear 10mo ago

Doesn't the browser automatically a handle locales when using the HTML5 input=date?

folmar 10mo ago
Even if, that does not help. When asked for a birthday I need validation of the date in country when I was born, not the country I'm in, not the locale I'm using for display and not the locale server/requesting company is in.
- jrochkind1 10mo ago
  I am thinking about locale of how a date/time is formatted for display/input. Including language-specific month names etc.

dotancohen 10mo ago

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

tlamponi 10mo 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 10mo ago
  That is called input assistance, confusing it with validation is the source of millions of security problems.
  - __jonas 10mo ago
    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-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 10mo ago
      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.
  - tlamponi 10mo ago
    No, it's not. And if that's what confuses one, it will not be the actual source of these problems.