News for hackers. Stuff that matters.
Re:The Sad State of HTML Email Input Fields and IDNs by jstanley on Sunday October 23, 2016 @10:36AM (#12773732)
> Despite the user’s locale being de_DE.

Surely you're not suggesting that the representation of the date that is returned by the browser should be locale-dependent? That would be a nightmare.

Re:The Sad State of HTML Email Input Fields and IDNs by kuschku on Sunday October 23, 2016 @12:43PM (#12774234)
Well, it’d be less of a nightmare than returning it in a random locale!

At least when it’s locale-dependent I can use a look up table and parse it somehow, but getting it back in MM/DD YYYY?

I’d love to just get ISO8601 ideally, btw, but who knows if that will ever happen.

(Also, you should check out Microsoft Excel, its date type and CSV converter are both locale-dependent. Locale of the program opening the file, not the file itself. A file created in de_DE will be unusable in en_US)

Re:The Sad State of HTML Email Input Fields and IDNs by rch on Sunday October 23, 2016 @06:14PM (#12775682)
Do not look at Excel when thinking about appropriate handling of dates and times.
Re:The Sad State of HTML Email Input Fields and IDNs by mathw on Monday October 24, 2016 @04:21AM (#12777337)
It makes a fantastic checklist of things you shouldn't do while handling dates though!