Support of the jQuery-ui datepicker's altField about jquery-serialize-object HOT 1 CLOSED

This is certainly not the responsibility of this plugin.

I don't know what nightmare you're experiencing with JSON and dates. I suspect it's one of timezones.

// run at 12:21 CDT -5
JSON.stringify(new Date());
// => '"2015-07-08T17:21:39.290Z"'

If you actually use a JavaScript Date object, it will automatically be converted to UTC (GMT).

As for using the JSON date value? Well watch what happen when I take the JSON time and pass it back to the Date constructor

Date("2015-07-08T17:21:39.290Z");
"Wed Jul 08 2015 12:24:46 GMT-0500 (CDT)"

I get my original time back. Notice how it's even displaying my correct timezone even though the JSON time string is in UTC. This is because JavaScript is aware of my current timezone offset.

There's nothing inherently wrong with date/time in JSON — you or your plugin are probably just misunderstanding some fundamental concept.

If you're not using Date objects to generate the correct date strings in your JSON, then yes, you'll likely be in a nightmare situation.

If your plugins are filling in form values for you and they're not using date.toString(), then yes, you'll likely be in a nightmare situation.

The solution isn't to offload responsibility to other plugins (such as this one) to detect/use some gimmicky altField element. The solution is for them to fix their garbage plugin or for you to use a better solution altogether.

from jquery-serialize-object.