81–90 of 97 posts
Earlier quoted context omitted.
I have, occasionally, thought that (for example) October = 8th month because it starts with "Octo". Yes, I know, historically it was.
That would be cool. So June would be Hexember, Hexober, or Hexuabry. January would be odd though - Mono-vember.
What really bothers me is that most of time when the date of birth is asked it is done as a way to determine some age criteria. The same could be achieved simply asking "are you older than N years old? [Yes] or [No]". For example, I want to buy Quake on the Nintendo eShop. The website wants to know my age in order to show me a age restricted game. So it will always ask me the age same question even if I have already…
> As a small revenge I always use an absurdly old birth date on these forms. This way if they are collecting this data, my input will be discarded or pollute their datasets. Or the micro-frauds get detected, linked to your credit card & email address, your identity, and credit rating. Before you know it, your transactions are failing fraud checks, you can't get loans, and BigTechs unilaterally cancel your accounts. I…
author here, just to note our current design pattern for this is slightly updated: https://design-system.service.gov.uk/components/date-input/
Very cool to see author responses on an article from 2013! I was wondering why you chose to use the placeholder attribute to show labels rather than the (afaik recommended) usage of showing example values. The form shows example values, but outside the input fields. Did you test both ways and this turned out to be better after all, or this was just an implementation which worked fine in testing so it stuck?
I've seen some US government forms use [01] [Jan] [1970] where [01]: one- or two-digit day, typed manually [Jan]: three-letter month, picked from a dropdown [1970]: four-digit year, typed manually I think this is a good (the best?) presentation. By using a manual day entry instead of providing a dropdown, as the programmer you can avoid requiring client-side logic to restrict the number of days displayed in the dropd…
> I think this is a good (the best?) presentation. I don't think so. It has problems with i18n. For example, the abbreviation for December is "Dic" in spanish and "Dez" in German, not "Dec" as in english.
Earlier quoted context omitted.
> As a small revenge I always use an absurdly old birth date on these forms. This way if they are collecting this data, my input will be discarded or pollute their datasets. Or the micro-frauds get detected, linked to your credit card & email address, your identity, and credit rating. Before you know it, your transactions are failing fraud checks, you can't get loans, and BigTechs unilaterally cancel your accounts. I…
Literally no part of this makes sense. You can fear anything you want, but this scenario only exists in your imagination.
Earlier quoted context omitted.
I tried to help my boss once to log onto Zoom for a meeting. The site asked for date of birth, and not wanting to give any PII I naturally entered some bullshit but plausible date. Well Zoom locked him out for some time for trying to lie I guess and that meeting had to be moved to Teams.
This is interesting. What triggered them to think this was a lie? Had your boss previously entered a different birthdate, which they remembered and then compared to?
One thing I always felt was an anti-pattern was in any input where months are numbers they don't explicitly mention in an adjacent label the name of the month. Besides the US/UK order confusion, you'd be surprised how often people think August is the 7th month of the year.
Jan01, Fev02, Mar03, Apr04, May05, Jun06, Jul07, Ago08, Sep09, Oct10, Nov11, Dec12
I've seen some US government forms use [01] [Jan] [1970] where [01]: one- or two-digit day, typed manually [Jan]: three-letter month, picked from a dropdown [1970]: four-digit year, typed manually I think this is a good (the best?) presentation. By using a manual day entry instead of providing a dropdown, as the programmer you can avoid requiring client-side logic to restrict the number of days displayed in the dropd…
For other dates though maybe, since most wouldn't have all month numbers memorized, but I’d still say typed, only with a variation on month name (you should be able to parse both abbreviated and full, so long as you know their locale) is better all the time.