-
Notifications
You must be signed in to change notification settings - Fork 299
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
Input marked dirty after updating to Angular 17 #1357
Comments
We are facing the same issue. Thank you for providing a version to fallback to in the meantime. |
I'm seeing this behavior when upgrading from ngx-mask 17.0.5 to 17.0.6 I forked the above stackblitz and just backed off to 17.0.5 and the input is not dirty |
Do you have an approximate time frame when this fix (1358): add trailing zero when mask="separator.1" and leadZero="true" will work with Angular 17 ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we updated from Angular 16 to Angular 17 (which included updating related libraries like ngx-mask), we faced a regression. A input field in a form was marked dirty right after initialisation. I created a StackBliz to reproduce the problem. Just click the button "Check dirty" and you will see as output that the input field using ngx-mask is dirty while the others are not dirty. All are assigned the same way.
I am not sure if this is related to a number of other issues that are already closed regarding wrong "dirty" behavior.
As a workaround we are currently using Version 16.4.2 of ngx-mask with Angular 17. This seems to work.
The text was updated successfully, but these errors were encountered: