NSSecureTextField and dead chars (umlauts, etc)
NSSecureTextField and dead chars (umlauts, etc)
- Subject: NSSecureTextField and dead chars (umlauts, etc)
- From: Evgeny Yakovlev <email@hidden>
- Date: Tue, 06 Sep 2011 17:04:55 +0700
Hi,
I noticed a very strange behavior. To type an umlaut vowel you have to
first type a dead char 'option + u' and then the actual vowel that
will be an umlaut, for example option + u and then 'a' will print ä.
The same goes for accents, etc just using a different dead char combo.
Normal NSTextField accepts these characters no problem. But
NSSecureTextField just drops the dead char and only takes what
follows. Instead of 'ä' it will only get 'a' because it dropped
'option + u'.You can actually try this out on any system password
field. Instead of any vowel in your password just type it accented or
umlaut'ed using corresponding dead char combo. The passwords will
match, because dead char was dropped.
Now for my application this is completely unacceptable, because i am
dealing with entities with passwords created on Windows and Linux
where umlauts do get passed. Since i can't type an umlaut in
NSSecureTextField on Mac i can't provide a correct password even if i
know it!
I tried playing around with NSSecureTextFieldCell
setAllowedInputSourceLocales: but with no result.
Are there any known workarounds?
Inso Reiges
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden