TextField secure="true" and keyboardType="number" input not secure, and keyboard is default
See original GitHub issueWhen set Text field TextField secure=“true” and keyboardType=“number” input not secure, and keyboard is default
<TextField row="0" col="2" hint="CVV" class="input input-border" secure="true" keyboardType="number" maxLength="3"></TextField>
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Native UITextField Secure Text Entry forces English (US ...
It will force change the locale in the keyboard. private func textConfigure(textField: UITextField) { textField.keyboardType = .default ...
Read more >A QWERTY keyboard is not shown whe… - Apple Developer
newPassword, a QWERTY keyboard is shown. In iOS14.2, if we tap a password text field(It means the text field which isSecureTextEntry is true)...
Read more >Text field - Adobe Spectrum
Text fields allow users to input custom text entries with a keyboard. Various options can be shown with the field to communicate the...
Read more >SwiftUI TextField: Keyboard Types - DevTechie
keyboardType modifier. For our next screen we will ask users to enter their phone number, age, name, a security phrase, email address. Which...
Read more >Specify the input method type - Android Developers
Every text field expects a certain type of text input, such as an ... the appropriate soft input method (such as an on-screen...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@NickIliev Setting secure and numeric keyboard type results in plain unsecure text keyboard shown because TYPE_NUMBER_VARIATION_PASSWORD actually belongs to TYPE_CLASS_NUMBER, so the correct implementation should be:
/tns-core-modules/ui/text-field/text-field.android.ts
Hi @deepak4u2006,
the fix is available in the
next
version of tns-core-modules and is going to take part of version 3.4.0 expected in a few weeks.