Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.5.0-preview.2
Issue ID
1219367
Regression
Yes
[TextMesh Pro] Text floats to the left when Input field is overflowed on certain package versions
How to reproduce:
1. Open the SampleScene Scene in the attached "1219367.zip" project
2. Enter Play Mode and enter some text in the first two input fields
Expected result: Both of the Input Fields, when overflowed with text, the beginning of the text is not seen
Actual result: The top Input Field, when overflowed with text, floats to the left outside of the Input Field
Reproducible with: TextMeshPro 1.5.0-preview.2 (2019.2.20f1, 2019.3.2f1, 2020.1.0a14),TextMeshPro 2.1.0-preview.2 (2019.3.2f1,2020.1.0a14), TextMeshPro 3.0.0-preview.4 (2020.1.0a14)
Not reproducible with: TextMeshPro 1.5.0-preview.1 (2019.2.20f1, 2020.1.0a14) TextMeshPro 2.1.0-preview.1 (2019.3.2f1, 2020.1.0a14)
Could not test with: TextMeshPro 1.2.2 from Asset Store (2017.4.37f1), TextMesh Pro 1.5.0-preview.1 (2018.4.18f1), TextMesh Pro 1.5.0-preview.2 (2018.4.18f1), TextMeshPro 2.1.0-preview.1 (2019.1.14f1), TextMeshPro 2.1.0-preview.2 (2019.1.14f1) (Missing Components and references)
Notes:
-Both settings of the TMP Input Fields are identical (except for the position)
-When testing with TMP 2.0.0 all of the Text slides to the right
-When testing with TMP 3.0.0-preview.3, TMP 3.0.0-preview.4 can only reproduce when commenting out certain parts of the code that causes compiler errors
-The workaround is to toggle Rect Mask 2D (Component) on the "Text Area" GameObject that belongs to the "Bugged" Input Field-TextMeshPro GameObject
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Two package versions of TextMesh Pro (1.5.0-preview.2, 2.1.0-preview.2) causes this issue where the Input Field child "Text Area" GameObject Component "Rect Mask 2D" gets disabled and the toggle is ignored. Workaround: update package to a newer version and enable the component "Rect Mask 2D"