I'm still facing that issue with current PrimeNg 17 and created a new PrimeNg bug report with stackblitz example for reproduction: https://github.com/primefaces/primeng/issues/16729
Let's see, what the PrimeNg team can do...