❓Question: emitEvent: false behavior when using ngx-mask directive

[gloammer]

Description

I encountered an issue with the emitEvent: false behavior when using ngx-mask directive. When two FormControls depend on each other and mutually update values, the emitEvent: false option doesn't work as expected with masks applied.

Here's a minimal reproduction case: https://stackblitz.com/edit/angular-kzjbyusr?file=src%2Fmain.ts

Case 1 (without mask directive):
When using emitEvent: false, changing a value in controlX shows only one log controlY.setValue in the console, and vice versa - this is the expected behavior.

Case 2 (with mask directive):
When using emitEvent: false, changing a value in controlX shows two logs: controlX.setValue and controlY.setValue in the console, and vice versa. This means emitEvent: false is not working properly.

I expect the behavior to be consistent whether a mask is applied or not. The emitEvent: false option should prevent additional value change emissions regardless of mask usage.

Question: Is this emitEvent: false behavior with masks expected, or should it work the same way as without masks?

Environment

• ngx-mask version: ^20.0.3
• Angular version: ^20.0.0

[jebner]

Any news on this?

[alinadanilaa]

this might also be worth looking into, its says It won't do this if writingValue is true. then in the function formControlResult it sets this.writingValue = false; Commit 54bc01a

[AYBox]

I encountered a similar issue with interdependent masked fields in Angular 21 when I upgraded form version 19.0.6 to 20.0.3

I have two numeric fields with mask that need to stay in sync.

When a user types in one field, the other should automatically update via calculation.

Using (ngModelChange) on both fields created a circular dependency. This was not a problem when using version 19.0.6.

(Switching to (input) events resolved the issue since input only fires from actual user interaction, not programmatic value changes.)