Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.40f1
2022.3.37f1
6000.0.10f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-75410
Regression
No
Text Styles are not applied to Underline and Strikethrough when TextMeshPro text without tags is used
Reproduction steps:
1. Open the attached “Test_TMPro_styles.zip” project
2. Open the “SampleScene” scene
3. Observe the “Text_1” and “Text_2” TextMeshPro GameObjects
Expected result: Both GameObjects look the same
Actual result: “Text_1” GameObject does not have Text Style applied to Strikethrough and Underline Font Styles
Reproducible with: 2021.3.40f1, 2022.3.37f1, 6000.0.10f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- The issue is reproducible with most Text Styles (except “Normal”, “Quote” and “Title”)
- The issue does not reproduce if tags “<s>” or “<u>” are used, like in “Text_2” 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
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
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.