Hi Fabrice Guichard,
Thank you once again for your patience.
We would like to inform you that the reported issue has been resolved in the latest version of our package. The behavior appears to have been addressed as a result of another recent fix.
To take advantage of this improvement, we kindly recommend updating your package to the latest version. For your reference, we have prepared an updated sample which you can access from the link below:
Updated Sample:
https://stackblitz.com/edit/angular-xvwiycf7-vdgd7cf2?file=package.json
Regards,
Yohapuja S