Custom NSWindow styleMask behavior changed/broken resulting in unresizable or non-responsive windows in macOS Tahoe 26.3 RC

NSWindow objects with custom styleMask configurations seem to behave erratically in macOS Tahoe 26.3 RC.

For example an NSWindow is not resizable after issuing .styleMask.remove(.titled) or some NSWindow-s become totally unresponsive (the NSWindow becomes transparent to mouse events) with custom styleMask-s.

This is a radical change compared to how all previous macOS versions or the 26.3 beta3 worked and seriously affects apps that might use custom NSWindows - this includes some system utilities, OSD/HUD apps etc, actually breaking some apps.

Such fundamental compatibility altering changes should not be introduced in an RC stage (if this is intentional and not a bug) imho.

FB21879057

Hi Steve,

Thanks for the Feedback number. We've gotten a few similar reports on 26.3 RC and are investigating.

I am super relieved it's not only me hallucinating all this and others encountered this as well. :)

I narrowed down the issue to .styleMask.remove(.titled). Depending on other styleMask flags and NSWindow properties, this can result in (1) an inability to resize the window or (2) a kind of click-thru effect - the content does not seem to capture mouse events but the window acts as if it would be transparent to user interaction.

Custom NSWindow styleMask behavior changed/broken resulting in unresizable or non-responsive windows in macOS Tahoe 26.3 RC
 
 
Q