Oh no!

This weirdness about the popup button causing an inconsistency is due to my enabling the Pasteboard Privacy preview ( https://developer.apple.com/documentation/updates/appkit#macOS-pasteboard-privacy ) in the global domain.

Filed as FB21115331.

Also, the aspect where the activation of an NSPopUpButton causes semi-loss of key seems to be fixed in macOS 26. While it’s possibly an artifact of the migration to Cocoa menus, I’ll take it.

While the popup menu is showing, NSApp thinks the window hosting the popup button is key, but that window doesn’t think it’s key.

See https://crbug.com/456027008#comment5 for a sample project to experiment with.

I have no further details nor advice.

Like, I know it’s tricky, but like any good puzzle designer it’s meant to have an easy in. Who doesn’t know Wolverine claws when they see them? Apparently most people? And so the next step, who played Wolverine, is just too much, and the step beyond that is hopeless.

google.com/g/wireless-sensor-tags ) and it's not clear that they even are aware of this privacy incident.

the 2025 movie and I can feel it slip from my brain.

https://mifi.no/blog/automated-electron-build-with-release-to-mac-app-store-microsoft-store-snapcraft/#ffmpeg-private-api-usage ) but now it’s officially cool for everyone to use. Hurrah!

window control buttons, this IMPL is a good starting point for investigation.