NSAutoFillRequiresTextContentTypeForOneTimeCodeOnMac
As you’ve undoubtedly heard by now, macOS Tahoe brings Security Code AutoFill of delivered codes (via Messages and Mail) to all Mac apps, including web browsers, without text field content type annotations. This matches the iOS behavior since iOS 12.
We’ve published some documentation about this new behavior, as well as how Mac apps can opt out of being eligible for one-time codes (without annotating fields) via a new Info.plist key.
I don’t really understand why this is opt-out, since it seems like it isn’t relevant to 99% of the text fields on my Mac. Are the expectations so low about apps that would benefit doing the work to opt-in? However, it’s great news that this system is being opened up to third-party browsers and apps.
Previously:
2 Comments RSS · Twitter · Mastodon
True, it’s not relevant to most text fields, but how often do you receive these codes? On the rare occasion you do receive a code, you’re likely focused on, or about to focus on, the text field that needs it. I suspect opt-out is a reasonable default.
@Rob Yeah, that makes sense, and it’s not the end of the world if it offers auto-fill in the wrong field.
