Input marked dirty after updating to Angular 17

[patrickuhlmann]

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.

[achapman009]

16.4.2

We are facing the same issue. Thank you for providing a version to fallback to in the meantime.

[joelryan2k]

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

[matviienko-danylo]

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 ?