Striker@lemmy.worldM to Mildly Infuriating@lemmy.worldEnglish · 1 year agoThis mofo was born on the wrong daylemmy.worldimagemessage-square45fedilinkarrow-up1399arrow-down126
arrow-up1373arrow-down1imageThis mofo was born on the wrong daylemmy.worldStriker@lemmy.worldM to Mildly Infuriating@lemmy.worldEnglish · 1 year agomessage-square45fedilink
minus-squareTheSpermWhale@lemmy.worldlinkfedilinkEnglisharrow-up11arrow-down15·1 year agoI think it’s using the daft American date system of m/d/y
minus-squarethatsTheCatch@lemmy.nzlinkfedilinkEnglisharrow-up17·1 year agoBut it says ‘DD/MM/YYYY’ just above the input field
minus-squaresfgifz@lemmy.worldlinkfedilinkEnglisharrow-up11·1 year ago 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!
minus-squareCeeBee@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoI’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.
I think it’s using the daft American date system of m/d/y
But it says ‘DD/MM/YYYY’ just above the input field
Dev: But it works fine on my system!
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.