How am I holding SecureField wrong because macOS Passwords integration can’t be this broken can it?!

[mhp@mstdn.ca]

How am I holding SecureField wrong because macOS Passwords integration can’t be this broken can it?!

The translucent overlay prevents clicks 🫠

/cc @rmondello

[rmondello@hachyderm.io]

@mhp I am actively trying to figure out why this happens and how to fix it. It’s giving me grief!

[mhp@mstdn.ca]

@rmondello I’m here to help!

phew not a me problem like it usually is

[mhp@mstdn.ca]

@rmondello i can confirm it affects NSSecureTextField and SecureField if the textContentType is `password`. Building with Xcode 26.3 but also on a 2 year old build for the AppKit variant. `newPassword` it doesn’t appear but the option-click presents AutoFill > Passwords and the popover is unaffected (but not in create password state)

Thought it was because it was presented from a sheet, but in the window view, sheet, or alert all exhibit the same behaviour.

Looks like the Xcode account sign-in doesn’t set the contentType to password. Wonder if they hit it and worked around (or never set the content type for the secure text field ‍️)

[mhp@mstdn.ca]

@rmondello can confirm that with the content type set to `.password` and you don’t click the “Passwords” credential suggestion popover, and instead do the option-click AutoFill > Passwords it works.

Something coming from the credential suggestion popover adds an overlay and window controls