Or they check for MM/DD/YYYY but prompt for DD/MM/YYYY.
Comment on This mofo was born on the wrong day
Alexstarfire@lemmy.world 1 year ago
Could be a bug but the more likely explanation is that the field doesn’t update until you try to leave it. So you put in a wrong date first, try to leave the field, get error message, then type in valid date and save a pic before leaving the field.
Tb0n3@sh.itjust.works 1 year ago
grabyourmotherskeys@lemmy.world 1 year ago
Both of these are incorrect. YYYY-MM-DD for life.
driving_crooner@lemmy.eco.br 1 year ago
This post is approved by the ISO-8601 gang.
obvs@talk.macstack.net 1 year ago
For all of the people who like their files to be in chronological order.
luciferofastora@lemmy.zip 11 months ago
…along with calendar weeks being entire weeks, not bullshit like 5 days of CW 53 and 2 of CW 1. This matters when dealing with BI facts that continue through NYE.
Do you know how infuriating it is to view analytics by calendar week with two major dips around new year’s because the week is split in two?
Bonus points: “Sure, you can set the week aggregation to consider weeks starting with Monday, but if you filter for the last X calendar weeks, you’ll have the last week’s sunday omitted from the stats and an orphaned Sunday before the first week yoh actually wanted.”
Support international standards, you bloody imbeciles.
grabyourmotherskeys@lemmy.world 11 months ago
I am intimately familiar with issues like this. It’s maddening.
sepiroth154@feddit.nl 1 year ago
Or it checks for the one without spacing and doesn’t remove the whitespace.
neoney@lemmy.neoney.dev 1 year ago
Or it expects the user to be 18 and has an awful error.
wreckedcarzz@lemmy.world 1 year ago
Ding ding, this is the likely answer. I’ve seen this exact issue before on multiple sites and services, and it’s always been found that the form expects 18+.