3 ms·

What makes you think they don't? But they still want good UX for entering the data.

• klingonopera 7y ago
  Insistence on (EDIT: having used) using type=number. Given the choice of bad UI vs. (accidentally) modified data, I'd pick bad UI any day. Insistence on using number makes me suspect they require sanitation to be done client-side. EDIT: Normally, I wouldn't assume a website run by a government wouldn't be doing this, but wasn't there some scandal recently in the US about the Dems and some web-app, and that it was woefully amateuristic? Suffice to say, that has kinda changed my perception about governments and IT. Then again, "gov.uk" has a tech blog, so I'm probably misplacing my skepticism. EDIT2: Updated tense.
  • yazboo 7y ago
    The article is recommending against using type=number.
    • klingonopera 7y ago
      ...which they're only doing, after having it done.
      • petepete 7y ago
        Because at the time it was the best way to have mobile apps show the numeric keypad instead of the regular keyboard. Keep up.
  • jkrems 7y ago
    > Insistence on using number makes me suspect they require sanitation to be done client-side. Why when they explicitly state that it was done for getting the proper input UX on mobile? The whole article is about finding a good UX for inputting numbers, taking different device types and accessibility concerns into account. It doesn't mention using these for validation at all afaict. Somewhere in this thread one of devs showed up and explicitly stated that they disable all HTML validation on the pages.