Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Datepicker] offset -1 #6871

Closed
rvoltolini opened this issue Sep 6, 2017 · 7 comments
Closed

[Datepicker] offset -1 #6871

rvoltolini opened this issue Sep 6, 2017 · 7 comments
Assignees

Comments

@rvoltolini
Copy link

Bug, feature request, or proposal:

Bug

What is the expected behavior?

Start Month at day 1

What is the current behavior?

Start Month at day 31 (offset -1), when i select the date at datepicker the date in input is updated correctly.
This error also happens when I select the month

captura de tela de 2017-09-06 10-21-58
captura de tela de 2017-09-06 10-24-14
captura de tela de 2017-09-06 10-26-48

What are the steps to reproduce?

Open Datepicker in https://material.angular.io/components/datepicker/overview

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

OS Ubuntu 17.04 (update today)
Chrome/Firefox (update today)

Is there anything else we should know?

Last week I didn't have problems, I used a lot of times testing the system that I'm developing.
I updated the OS thinks this could be the problem, but I didn't get sucess

@julianobrasil
Copy link
Contributor

@mmalerba, it seems to be related to that daylight saving time issue...

@mmalerba
Copy link
Contributor

mmalerba commented Sep 6, 2017

@julianobrasil have you had any luck reproducing? It looks normal for me

@rvoltolini
Copy link
Author

I think not. Daylight in Brazil starts in october.
I opened Datepicker in other Pc and it worked normally.
I think it's something in my notebook but i don't know how discovery it.
I updated OS, deleted node_modules (including home folder), change angular/material version (beta 10 and 8) and the problem remained.

@julianobrasil
Copy link
Contributor

julianobrasil commented Sep 6, 2017

@julianobrasil have you had any luck reproducing? It looks normal for me

@mmalerba, not really. I tried out with known past dst dates which I used as testing cases (and also tried a lot of other dates, over a decade), but with no luck.

It looks like a new issue, maybe caused by some particular configuration as @rvoltolini mentioned.

@jt-helsinki
Copy link

I think this is related to #7167

@mmalerba
Copy link
Contributor

likely dupe of #7167

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants