Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b21
Issue ID
670861
Regression
Yes
TouchScreenKeyboardType doesn't work
TouchScreenKeyboardType doesn't work
1. What happened
In 5.0b21-5.0f1 (those are what I've tested, not where it regresses to) TouchScreenKeyboardType does not pull up the correct keyboard when a GUI.TextField tapped on.
I've tried this on both Tizen phones and BlackBerry phones; I'd imagine therefore it happens on other mobile touchscreen phones.
I'll try regression testing and porting it to iOS if I get time. If you really want me to look into anything else on this just shoot me an email.
2. How we can reproduce it using the example you attached
To repro:
1) Deploy project to phone
2) Tap in TextField in center of screen
3) Select any of the buttons below the textfield numbered 1-7 (example #5)
4) Notice the GUI.Label "Keyboard:" + x changes (example "PhonePad")
5) Tap in the textfield again - the keyboard doesn't change (example a dialing pad isn't spawned, it's a plain old keyboard.)
Public status: Public
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment