I just had a chance to verify and in fact the problem does not occur on macOS 12.6. So it seems that this is a bug that has been introduced in macOS 13. Still, the question remains if there is a workaround from a developer's perspective...