Vuetify: Pick wrong date in text field

[CasperLaiTW]

Steps to reproduce

1. open https://vuetifyjs.com/components/pickers
2. Section #3 Date pickers - In dialog and menu
3. Click TextFields
4. Pick a date
5. Get date after 1 month and 1 day on textfield

Versions

Vuetify: 0.16.0
Browser: Chrome 61.0.3163.100

Reproduction Link

https://vuetifyjs.com/components/pickers

[KaelWD]

What timezone are you in?

@jacekkarczmarczyk Looks like it might be that timezone bug back again...

[CasperLaiTW]

My timezone is +08:00

[johnleider]

Can you please check one more time to see if this issue is happening.

[jacekkarczmarczyk]

This issue might occur on some specific hours, so it's best if you check at the same time of the day as before (and write in comment what time did you check)

[nekosaur]

Or you know, change the system time :)

[jacekkarczmarczyk]

I know, but system automatically reverts to the real time, probably it could be blocked somewhere

[KaelWD]

[jacekkarczmarczyk]

OK, I didn't see this because it shows only when you're logged in as an admin

[CasperLaiTW]

Hi, I recorded my screen.
This is my local time, Friday, 6 October 2017.

And this is using picker and get results.

Section #1, Section #2 and Section #4 display date is correct, but day of week in head is wrong. 5th Oct. is thursday not friday.

Section #3 and Section #5 is wrong when pick

[jacekkarczmarczyk]

That's weird, the information given by you looks perfect, however I still cannot reproduce it... I've set CST+8:00 time zone and checked now in Chrome/Firefox/Explorer/Edge and everywhere I'm getting correct results :/
Can you run Intl.DateTimeFormat().resolvedOptions().timeZone and new Date().toISOString() in console and send the result?

[CasperLaiTW]

something interesting, I got timezone America/Chicago

But my system time zone is Taipei Standard Time. weird.

[jacekkarczmarczyk]

Last question (for now) - what browser are you using?

EDIT: If it's safari then I've found something this: https://github.com/moment/moment-timezone/issues/502

[CasperLaiTW]

Chrome Version 61.0.3163.100 (Official Build) (64-bit)

[KaelWD]

Open Terminal and run echo $TZ

[jacekkarczmarczyk]

And run this in console new Date()
And BTW maybe you can chat on discord channel? https://chat.vuetifyjs.com

[CasperLaiTW]

@KaelWD got nothing.

@jacekkarczmarczyk got timezone is +00:00

[peluprvi]

I found some related issues in moment.js:
https://github.com/moment/moment-timezone/issues/441
https://github.com/moment/moment-timezone/issues/517

They use Intl.DateTimeFormat().resolvedOptions().timeZone too.

[eelcowen]

I found that March was duplicated in my view:

I clicked in March 1 and the date correctly got selected.

Then i went one month further and I see March again....

Now i click on March one and April two gets selected....

new Date().toISOString()
"2017-10-09T08:07:59.804Z"

Intl.DateTimeFormat().resolvedOptions().timeZone
"CET"

[jacekkarczmarczyk]

What vuetify version?

[eelcowen]

Latest 0.16.4

I'm digging now and i get an error VDatePicker.js --> computed --> timeZone --> catch block
RangeError: Expected Area/Location(/Location)* for time zone, got CET

[jacekkarczmarczyk]

and chrome@OSX?

[eelcowen]

Yes

[KaelWD]

Looks like a chrome bug from a few years ago: https://bugs.chromium.org/p/chromium/issues/detail?id=364374

[elceka]

Chrome 61.0.3163.100
OSX 10.11.6

March 2017 multiple 26 day in order.

[elceka]

Error presence from the Vuetify version 0.16.0-beta.5, in the version 0.16.0-beta.3 is not this error.
Tested on the same environment then i wrote before.

[peluprvi]

@elceka Did you tried it on v0.16.5?

[elceka]

@peluprvi Please, check my issue #2156

[jacekkarczmarczyk]

@elceka can you check your issue using the following template https://codepen.io/CasperLai/pen/MEGJOL? (Use your code, don't change external javascripts)
It uses Vuetify with PR that should fix time zone related issues

[elceka]

@jacekkarczmarczyk Seems like be OK with that template.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord