Search Issue Tracker
Fixed in 3.0.3
Fixed in 1.5.3, 2.1.3
Votes
0
Found in [Package]
2019.4
2020.1.3f1
2020.2
Issue ID
1272647
Regression
No
TMP_InputField Vertical Scrollbar sometimes snaps to the top when value of "1" is assigned
How to reproduce:
1. Open attached "case_1272647.zip" project and Scenes/SampleScene scene
2. Enter the Play mode
3. Select the Input field that is on the bottom in the Game view
4. Enter any text and press Enter
5. Keep repeating step #4 and observe the Scrollbar of the Input field that is above
Expected result: Scrollbar is positioned at the Bottom
Actual result: Scrollbar sometimes snaps to the top
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1 (TextMeshPro 2.0.1 - 3.0.1)
Could not test with: 2018.4.27f (could not downgrade)
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 3.0.3):
Made several improvements to the Input Field with respect to handling and behavior when a scrollbar is used.
The input field now appears to be behaving correctly with the provided user project and without any modifications. I would still recommend using the revised code I provided to the user but both will now work as expected.
The fix for this issue will be included in the next release of the TMP package which is expected to be version 1.5.2 for Unity 2018.4, version 2.1.2 for Unity 2019.x and version 3.0.2 for Unity 2020.x.
Resolution Note (fix version 2.1.3):
Fixed in: 2.1.3
Resolution Note (fix version 1.5.3):
Fixed in: 1.5.3