You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the timepicker component is used not in template driven forms mode (i.e. not with ngModel binding but with an input formControl), the formControl status changes are always triggered although the value does not change.
This happens only if the minDate and maxDate are specified.
If the timepicker component is used not in template driven forms mode (i.e. not with ngModel binding but with an input formControl), the formControl status changes are always triggered although the value does not change.
This happens only if the minDate and maxDate are specified.
In html template
<input [class.color-transparent]="dialogOpen == true && !originalValue" matInput placeholder="{{placeholder | translate}}" [formControl]="timeFormControl" (timeChange)="focusIn == false ? timeChangeHandler('timechange') : ''" (invalidInput)="onInvalid($event)" (focusin)="focusIn = true" (focusout)="focusIn = false; timeChangeHandler('focus')" #t="matTimepicker" matTimepicker mode="24h" okLabel="{{okLabel | translate}}" cancelLabel="{{cancelLabel | translate}}" [disableDialogOpenOnClick]="true" [minDate]="minDate" [maxDate]="maxDate" [required]="required" >
In ts
@input() timeFormControl: FormControl = new FormControl(null);
` ngOnInit() {
moment.locale(this.translate.currentLang);
}`
The same happens for the valueChanges observable
Would it also be possible to accept undefined minDate and maxDate?
Thank you.
The text was updated successfully, but these errors were encountered: