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

ExpressionChangedAfterr... #66

Closed
ljjolic opened this issue Nov 7, 2018 · 6 comments
Closed

ExpressionChangedAfterr... #66

ljjolic opened this issue Nov 7, 2018 · 6 comments

Comments

@ljjolic
Copy link

ljjolic commented Nov 7, 2018

My timepicker is in a mat-form-field with <input matInput.....

I get this error when the timepicker pops up
ExpressionChangedAfterItHasBeenChcekedError;

any ideas ?
Thx

@Agranom
Copy link
Owner

Agranom commented Nov 7, 2018

Yeah, I know, it will be fixed in the next release. I'll notice you

@Agranom Agranom closed this as completed Nov 7, 2018
@Agranom Agranom reopened this Nov 7, 2018
@adrianzaorski
Copy link

adrianzaorski commented Nov 13, 2018

@Agranom I have similar issue, gonna provide you details so maybe it would be helpful.
Opening a timepicker causes an error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'ng-untouched: true'. Current value: 'ng-untouched: false', but only once - as far as my main dialog is open I can close or open the timepicker and there are no errors, it happens only once after opening a dialog window with inputs.

Code:

    <input matInput
           formControlName="from"
           placeholder="Available from"
           [ngxTimepicker]="picker"
           [format]="24"
           required
           readonly>
  </mat-form-field>
  <ngx-material-timepicker [minutesGap]="5" #picker></ngx-material-timepicker>

@derSoerrn95
Copy link

derSoerrn95 commented Nov 17, 2018

I'm having the same issue. @adrianzaorski did u find a solution?

@Agranom
Copy link
Owner

Agranom commented Nov 20, 2018

I hope it's fixed. Update to the latest version and check please

@derSoerrn95
Copy link

yes, nice 🙂

@Agranom Agranom closed this as completed Nov 20, 2018
@adrianzaorski
Copy link

Yeah, just to confirm - after update everything is working fine and there is no error, thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants