all 50 comments

sorted by: hot top controversial new old
[–] 72 points 2 years ago (3 children)

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.

  • source
  • hideshow 6 child comments
  • [–] 48 points 2 years ago (1 child)

    Or they check for MM/DD/YYYY but prompt for DD/MM/YYYY.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 81 points 2 years ago (3 children)

    Both of these are incorrect. YYYY-MM-DD for life.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 2 years ago (1 child)

    ...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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 37 points 2 years ago

    Do we have a community yet for IAm14AndThisIsFunny?

  • source
  • [–] 35 points 2 years ago (1 child)

    Another possible case no one seems to have mentioned. That the CSS doesn't do that kind of spacing automatically, and that the user manually put in spaces this creating an invalid date for the lulz.

  • source
  • hideshow 2 child comments
  • [–] 21 points 2 years ago (2 children)

    Still software gore. Spacing should not matter, proper parsing should ignore whitespace in a simple format like this.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 34 points 2 years ago (3 children)

    Maybe it's for something 18 and up? Like a banking app

  • source
  • hideshow 6 child comments
  • [–] 15 points 2 years ago (1 child)

    Remind is a communication platform that reaches students and families where they are and supports learning wherever it happens.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 years ago

    There was nothing in the post indicating what app this was and "Remind" is a generic enough word, even if upper-cased, to make the service not obvious. It could be a porn-site for what we know, in which case that date should naturally be rejected.

  • source
  • parent
  • [–] 11 points 2 years ago

    I'm going to guess they typed 02/17/2008 the first time to denote Feb 17th as is fairly standard with American apps. It then told him it was invalid because there arent 17 months in a year because it was the wrong format. They typed it correctly after and took a screen shot before pressing submit. (Making it so the error was still on screen from the previous bad submission. )

    That is all just a guess though.

  • source
  • parent
  • [+] 25 points 2 years ago* (last edited 2 years ago)
    [–] 10 points 2 years ago (5 children)

    Just want to say that DD/MM/YYYY is the superior date format. 💪🗓️

  • source
  • hideshow 10 child comments
  • [–] 9 points 2 years ago (2 children)

    I don't understand. OP can you help?

  • source
  • hideshow 4 child comments
  • [+] -62 points 2 years ago* (last edited 2 years ago) (4 children)
  • [–] 52 points 2 years ago (1 child)

    It specifically requested DD/MM/YYYY format though.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (1 child)

    Yeah... I am stoned but this looks like it should be valid and there is just a bug in the code.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 years ago (1 child)

    I’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 2 years ago (1 child)

    Sometimes if the developers don't specify, the date format can follow clients' settings, which can lead to unpredictable results like this.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 2 years ago

    Image Transcription:

    A screenshot from the setup of the Remind mobile application with an image of a calendar and the text

    "What is your birthday?

    This will stay private to you and will help keep Remind safe

    Birthday

    DD/MM/YYYY"

    Followed by a text field that has been filled out with the date "17 / 02 / 2008".

    Below the text field is the red error text reading "Please enter a valid date"

    [I am a human, if I’ve made a mistake please let me know. Please consider providing alt-text for ease of use. Thank you. 💜]

  • source
  • [–] -4 points 2 years ago (1 child)

    I think it’s using the daft American date system of m/d/y

  • source
  • hideshow 2 child comments
  • [–] 17 points 2 years ago* (1 child)

    But it says 'DD/MM/YYYY' just above the input field

    EDIT: it's very possible that the input field library they use uses the American date format by default and they didn't change it...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 11 points 2 years ago (1 child)

    it's very possible that the input field library they use uses the American date format by default and they didn't change it...

    Dev: But it works fine on my system!

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago

    I'm happy that I taught the BA and project lead learned how to clear all site data for the application I work on. It has reduced the huge amount of

    "the issue is still there!"

    "Clear the cache"

    "It works now"

    And yes, I know I should be using something that notifies the browser to invalidate its cache. I'll add it to my mile long list of tickets.

  • source
  • parent
  • [+] -9 points 2 years ago (1 child)

    The only thing worse than mm/dd/yyyy is dd/mm/yyyy. Use a bloody different separator if you're writing dates correctly.

  • source
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)
  • [–] -2 points 2 years ago (1 child)

    It's already in use for mm/dd/yyyy. When I see slashes I expect that, when I see dots I expect dd.mm.yyyy, when I see hyphens I expect yyyy-mm-dd.

    And then comes along a random I guess Canuck and writes something totally incomprehensible.

  • source
  • parent
  • hideshow 2 child comments