StrikerM to Mildly InfuriatingEnglish • 1 year agoThis mofo was born on the wrong dayimagemessage-square45arrow-up1403arrow-down127
arrow-up1376arrow-down1imageThis mofo was born on the wrong dayStrikerM to Mildly InfuriatingEnglish • 1 year agomessage-square45
minus-square@Nouveau_BurnswicklinkEnglish52•1 year agoIt specifically requested DD/MM/YYYY format though.
minus-square@ChocrateslinkEnglish4•1 year agoYeah… I am stoned but this looks like it should be valid and there is just a bug in the code.
minus-square@[email protected]linkfedilinkEnglish5•1 year agoI’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.
minus-square@[email protected]linkfedilinkEnglish10•1 year agoSometimes if the developers don’t specify, the date format can follow clients’ settings, which can lead to unpredictable results like this.
minus-square@[email protected]linkfedilinkEnglish1•1 year agoYeah, I’d imagine you’d want to adapt for different locales. Here in the US, MMDDYY is pretty ubiquitous, but I’m sure it’s different in other countries.
minus-square@[email protected]linkfedilinkEnglish2•1 year agoI’ve experienced this kind of confusion first hand, so I know a thing or two.
It specifically requested DD/MM/YYYY format though.
Yeah… I am stoned but this looks like it should be valid and there is just a bug in the code.
I’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.
Sometimes if the developers don’t specify, the date format can follow clients’ settings, which can lead to unpredictable results like this.
Yeah, I’d imagine you’d want to adapt for different locales. Here in the US, MMDDYY is pretty ubiquitous, but I’m sure it’s different in other countries.
I’ve experienced this kind of confusion first hand, so I know a thing or two.