Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.15f1
2023.2.4f1
2023.3.0a18
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.0a1
Issue ID
UUM-59592
Regression
No
[TextMeshPro]Zero Width Space generated by TextMeshPro InputField set to single line mode causes a graphical glitch when using a font with an underlay effect and Sampling Point Size set to Custom Size
Reproduction steps:
1. Open the attached "ReproProj.zip"
2. Open "Assets/Scenes/SampleScene"
3. Observe the Game View
Expected results: No black dot to the left of the "Enter text..." text
Actual results: Black dot to the left of the "Enter text..." text
Reproducible with: 2021.3.34f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a18
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
- 2021.3.33f1 and 2022.3.15f1 versions were tested with the 3.2.0-pre.6 version of the TextMeshPro package
- In 2023.2 and 2023.3. streams the TextMeshPro package is no longer available as it was merged into the UGUI package
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.