Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

datepicker: invalid value on first load from moment #12118

Open
j-walker23 opened this issue Aug 8, 2021 · 4 comments
Open

datepicker: invalid value on first load from moment #12118

j-walker23 opened this issue Aug 8, 2021 · 4 comments
Assignees
Labels
P2: required Issues that must be fixed. type: bug
Milestone

Comments

@j-walker23
Copy link

Bug Report

Demo URL (required)*: https://datepicker-invalid-value-on-first-load-from-string-12075-pskwl4.stackblitz.io

Detailed Reproduction Steps

  1. Start date as moment object

List the affected versions of AngularJS, Material, OS, and browsers

  • AngularJS: 1.8.2
  • AngularJS Material: 1.2.3
  • OS: All
  • Browsers: All
  • Screen Readers:

Add anything else we should know

This was just fixed for string being the default last version.
I added the below to that ticket, but I added it too late. I should have just opened a new ticket. Sorry about that.

When DatePickerCtrl.prototype.updateErrorState is called with a moment date
if (this.dateUtil.isValidDate(date)) { is false
So this.ngModelCtrl.$setValidity('valid', date == null); runs and the ngModel ctrl valid key is set to false.

@j-walker23 j-walker23 added needs triage Issues that need initial triage type: bug labels Aug 8, 2021
@j-walker23 j-walker23 changed the title datepicker: invalid value on first load from string datepicker: invalid value on first load from moment Aug 8, 2021
@Splaktar Splaktar self-assigned this Nov 18, 2021
@Splaktar Splaktar added this to the 1.2.5 milestone Nov 18, 2021
@Splaktar Splaktar added P2: required Issues that must be fixed. type: bug and removed type: bug needs triage Issues that need initial triage labels Nov 18, 2021
@Splaktar
Copy link
Member

Thank you for opening this issue. Sorry that I didn't notice your comment in #12075 and address that as well in PR #12115.

@Splaktar Splaktar modified the milestones: 1.2.5, 1.2.6 Dec 21, 2021
@matrium0
Copy link

matrium0 commented Jan 2, 2022

@Splaktar it seems this bug is also present if you use the Luxon Adapter instead of the Moment Adapter

@Splaktar
Copy link
Member

Splaktar commented Jan 2, 2022

@matrium0 AngularJS Material doesn't have an official Luxon adapter. Which are you using?

@matrium0
Copy link

matrium0 commented Jan 3, 2022

Ah sorry, I noticed a similar bug in MatLuxonDateModule (installed via @angular/material-luxon-adapter) for Angular not AngularJS.

My bad! (still I choose to blame it a tiny little bit on the choice to "keep the name" Angular :D ). Thanks for your quick response!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P2: required Issues that must be fixed. type: bug
Projects
None yet
Development

No branches or pull requests

3 participants