Search Issue Tracker
Fixed in 1.4.2 & 2.0.2
Votes
0
Found in [Package]
1.4.0, 2.0.1
Issue ID
1172102
Regression
Yes
An additional 'NULL' character is sent into overridden 'Validate' method when entering characters into TMPro Input Field
How to reproduce:
1. Open attached 'project-1172102.zip' project
2. Enter Play mode
3. Enter any character into Input Field
4. Observe Console window
Expected result: one message is shown (containing inputted character's ASCII code)
Actual result: two messages are shown (one of which is NULL's ASCII code)
Reproducible with: 2018.4.5f1 (1.4.0, 1.4.1), 2019.1.13f1, 2019.2.0f1, 2019.3.0a11 (1.4.0, 2.0.1)
Not reproducible with: 2018.4.5f1, 2019.1.13f1, 2019.2.0f1 (1.3.0), 2019.3.0a11 (1.2.1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.4.2 & 2.0.2):
This issue has been resolved and the behavior will be as it was in version 1.3.0 of the TMP package. The solution for this issue will be in the next release of the TMP package which is expected to be version 1.4.2 for Unity 2018.3 or newer and version 2.0.2 for Unity 2019.x.