This problem has been resolved in macOS 13. That said, it's concerning that whatever the underlying fix was has not been back-ported to macOS 12.x. I worry the fix was unintentional since it has been fixed since early in the macOS 13 beta cycle. If the fix was intentional, that means Apple has known about the problem for months without fixing the issue in macOS 12.x, which seems unlikely. I hope this doesn't get reintroduced.
Topic:
UI Frameworks
SubTopic:
AppKit
Tags: