I have an input on my webpage that I am able to set the date on by getting an ISO string and pulling out the first 10 characters.

date = new Date();
dateInput.value = date.toISOString().substr(0,10);

This works perfectly. My problem is that when I try to get the date back out. I am getting the date one day off.

var newDate = new Date(dateInput.value);

I have also tried the following code to make up for it, but it is not always correct either

new Date(Date.parse(element.value) + 86400000)

So my question is: Is there an elegant way to get the correct date consistently. I have been looking around for a little while, but it seems there is not a lot of consistency with date parsing in Javascript.

I have an input on my webpage that I am able to set the date on by getting an ISO string and pulling out the first 10 characters.

date = new Date();
dateInput.value = date.toISOString().substr(0,10);

This works perfectly. My problem is that when I try to get the date back out. I am getting the date one day off.

var newDate = new Date(dateInput.value);

I have also tried the following code to make up for it, but it is not always correct either

new Date(Date.parse(element.value) + 86400000)

So my question is: Is there an elegant way to get the correct date consistently. I have been looking around for a little while, but it seems there is not a lot of consistency with date parsing in Javascript.

• javascript
• html
• forms
• date
• input

• Where is the value of date coming from? – Achrome Commented May 29, 2013 at 23:06
• think you will find good use for momentjs.com – krasu Commented May 29, 2013 at 23:06
• I have figured out a way to use the string it gives me by just never converting it into a Date, but I am still baffled as to why it is behaving like this. – duckbrain Commented May 30, 2013 at 14:46

6 Answers 6

If it's an actual date input on a supporting browser, then it will have a valueAsDate property. There's no need to parse it.

var newDate = new Date(dateInput.value + 'T00:00');

This will give the correct date in any timezone.

It's interpreting the date as UTC, which, for most time zones, will make it seem like "yesterday". One solution could be to add the time-zone offset back into the date to "convert" it to your local timezone.

You can also convert the input string from YYYY-MM-DD to MM/DD/YYYY and it then parse the date to get the correct answer.

EXAMPLE:

Don't use:

new Date(Date.parse('2018-09-28')) // Thu Sep 27 2018 19:00:00 GMT-0500 (Central Daylight Time)

Rather use

new Date(Date.parse('09/28/2018')) // Fri Sep 28 2018 00:00:00 GMT-0500 (Central Daylight Time)

(NOTE: I am in CDT)

Tested in Chrome, Firefox, Safari, old Edge, and IE.

as said by Marty the problem is the difference between the representation of the timezone of the input (UTC defined by W3C) and the JS timezone (local). The solution is to getTimezoneOffset (which is in minutes) and convert everything to milliseconds:

var today = document.getElementById("myInputDate").valueAsDate;
var tomorrow = new Date(today.valueOf() + 86400000 + (today.getTimezoneOffset() * 60000));

86400000 = milliseconds of a day

today.getTimezoneOffset() * 60000 = timezoneOffset in milliseconds

Try using .toLocaleString to get the date into the input, and add the time when parsing it, like this:

date = new Date();
dateInput.value = date.toLocaleString("sv-SE", {
    hour: "2-digit",
    minute: "2-digit",
    second: "2-digit"
});

And to get the value into a Date object use:

new Date(inputdateInput.value + "T00:00");

I wrote a little post about converting between Date objects and date inputs here