News for hackers. Stuff that matters.

A comment on The Sad State of HTML Email Input Fields and IDNs. Parent comment

Re:The Sad State of HTML Email Input Fields and IDNs by TeMPOraL on Sunday October 23, 2016 @10:45AM (#12773771)
One would think it should be simple in principle.

User side: just show/accept whatever the site owner wants, or if it's too difficult, stick to ISO 8601 (it's the standard, damn it).

JS side: just ISO 8601.

[ Parent | on HN ]
Re:The Sad State of HTML Email Input Fields and IDNs by skrebbel on Sunday October 23, 2016 @12:10PM (#12774079)
Why ISO? JavaScript has had a Date type since forever.
[ Parent | on HN ]
Re:The Sad State of HTML Email Input Fields and IDNs by TeMPOraL on Sunday October 23, 2016 @12:21PM (#12774133)
So Date type, then, but if we're talking input fields, they're also meant to be used with forms submitted without all that JavaScript cruft on top. So if you have to convert the date input to text for sending (or direct retrieval in code), I'd say just stick to ISO. Why? Because it's a standard.
[ Parent | on HN ]
Re:The Sad State of HTML Email Input Fields and IDNs by skrebbel on Sunday October 23, 2016 @02:49PM (#12774809)
Ahyes, I'm so stuck in JS-o-world that I forgot there's an actual text format called HTML. Thanks :-)
[ Parent | on HN ]
Re:The Sad State of HTML Email Input Fields and IDNs by hibbelig on Sunday October 23, 2016 @06:43PM (#12775787)
Why the format the site owner wants? Why not the format the user wants?
[ Parent | on HN ]
Re:The Sad State of HTML Email Input Fields and IDNs by TeMPOraL on Sunday October 23, 2016 @07:22PM (#12775914)
That could be a reasonable default, but you need to give the programmer control over the format, or else everyone will keep using JS-powered replacements.
[ Parent | on HN ]