This seems to be a bug in PrimeNG 16.6.0 that has been fixed somewhen around 16.7.1, I think. Upgrading to 16.9.1, the latest version for Angular 16, fixes that.