Issue with CoreUI Angular modal static backdrop

[anyplin]

Operating system and version: Linux Mint 22.1
Browser and version: Google Chrome Version 142.0.7444.175 (Official Build) (64-bit)
Angular version: v20.2.2

Hello,

I am using the CoreUI Angular Modal component and have encountered an issue when using a static backdrop. I am controlling the modal visibility via [cModalToggle]. However, when the modal is closed, the backdrop sometimes remains for a short period, preventing interaction with the underlying page until it is removed from the DOM.

Currently, I have implemented a workaround to programmatically remove the backdrop when closing the modal, but I suspect this is not the intended behavior. Am I missing something, or is this a known issue?

Thank you very much for your help.

[xidedix]

@anyplin
Are there any errors in the console?

[anyplin]

@xidedix

There were no errors in the console.

[xidedix]

@anyplin
Could you provide a minimal reproducible example of your issue?
You can use the following link, fork, modify, and share it back: stackblitz

[bernik1980]

@xidedix
I just had a similar issue, where the backdrop would not disappear:

I integrated the modal in the following way:

@if (dialog) {
<c-modal [visible]="true" (visibleChange)="dialogChange($event)">
...
</c-modal>
}

The modal will appear just fine, if the dialog var is set to an object.

But when the dialog var is set to undefined, the c-modal would disappear, but the backdrop remains.

I never had this issue before, so I assume this must be changed in some of the last version. (In the particular project, i updated @coreui/angular-pro from 5.5.17 to 5.5.24.)

I can workarround this issue, by changing the integration to this:

<c-modal [visible]="!!dialog" (visibleChange)="dialogChange($event)">
  @if (dialog) {
..
</c-modal>

Maybe you can have a look into it? If this is the intended behavior?

[anyplin]

@xidedix

This is the stackblitz where my issue occurs.
I am using Angular's Zoneless change detection, which triggers the behaviour I explained

[xidedix]

@anyplin @bernik1980 thanks for the heads up!
fixed in 5.5.25