News for hackers. Stuff that matters.
Re:A single-page app is almost always worse than a multi-pag... by rovek on Tuesday October 30, 2018 @12:16PM (#18338213)
If you didn't use JS for date pickers, you didn't have very inclusive browser support - especially for something like a healthcare website. [1]

Were the designs and layout of these SPA and HTML5/CSS3 website also identical?

[1] https://caniuse.com/#search=input%20date

Re:A single-page app is almost always worse than a multi-pag... by thrower123 on Tuesday October 30, 2018 @02:29PM (#18339877)
It's more than a little absurd that there isn't a passable date picker implemented across the major browsers. I have wasted far, far too much of my life fighting with different half-baked JS datepicker components already in my life.
Re:A single-page app is almost always worse than a multi-pag... by davvolun on Wednesday October 31, 2018 @10:10PM (#18350964)
Still better than supporting IE6.
Re:A single-page app is almost always worse than a multi-pag... by bunderbunder on Tuesday October 30, 2018 @12:36PM (#18338487)
If it's public facing, that's a huge concern.

If it's intended for business users, particularly if on an intranet site, it's often very easy to limit the number of browsers and versions you need to support to just a handful.

Re:A single-page app is almost always worse than a multi-pag... by Isofarro on Tuesday October 30, 2018 @04:11PM (#18340870)
The Web has been collecting dates from users in forms long before date-pickers existed.
Re:A single-page app is almost always worse than a multi-pag... by davvolun on Wednesday October 31, 2018 @10:09PM (#18350959)
The Web has been doing lots of things poorly for a long time as well. I know I've seen some implementations of date-pickers I don't like, and more old school implementations without date pickers that were just clumsy.
Re:A single-page app is almost always worse than a multi-pag... by nostrademons on Tuesday October 30, 2018 @07:02PM (#18341977)
86% isn't bad, particularly considering you can easily polyfill a date-picker in the missing browsers and attach it to input[type=date] elements.