Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
3.2.0-pre.3
4.0.0-pre.1
Issue ID
TMPB-82
Regression
No
GetPreferredHeight returns 0 when overflow linking TMP components if the first component text features two or more new lines in between the last visible character of the first box and the first visible character of the next box
Reproduction steps:
1. Open the attached “PreferredHeight.zip“ project
2. Open the “SampleScene” scene
3. Enter the Play Mode
4. Observer the Console
Expected result: The logged preferred height is not 0
Actual result: “LayoutUtility.GetPreferredHeight returns: 0” was logged
Reproduced with: 3.0.6 (2020.3.36f1, 2021.3.5f1, 2022.1.7f1, 2022.2.0a18, 2023.1.0a1), 3.2.0-pre.3 (2023.1.0a1)
Could not test with: 4.0.0-pre.1 (2023.1.0a1) - “NullReferenceException” error
Reproduced on: Windows 10, Windows 11, macOS Monterey 12.0.1 (Intel)
Note: Possibly the issue can be tracked to TMP_Text.CalculatePreferredValues, where the for loop on line 4051 generates a height value that is off by roughly -2^16
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:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.