StrikerM to Mildly [email protected]English • 2 years agoThis mofo was born on the wrong daylemmy.worldimagemessage-square47fedilinkarrow-up1405
arrow-up1405imageThis mofo was born on the wrong daylemmy.worldStrikerM to Mildly [email protected]English • 2 years agomessage-square47fedilink
minus-square@[email protected]linkfedilinkEnglish52•2 years agoIt specifically requested DD/MM/YYYY format though.
minus-squareChrislinkfedilinkEnglish5•2 years 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]linkfedilinkEnglish6•2 years 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•2 years 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]linkfedilinkEnglish2•2 years 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•2 years 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.