Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.69f1
6000.3.10f1
6000.4.0b9
6000.5.0a8
Issue ID
UUM-135959
Regression
No
"Parse Escape Sequence" option is not applied retroactively to existing TextMeshPro text
How to reproduce:
1. Open the attached project “IN-135907”
2. Open the “SampleScene”
3. Observe the text in the Game View
4. In the Project Settings window, toggle “TextMesh Pro → Settings → Parse Escape Sequence” off
5. Add a new “Text - TextMeshPro” to the Canvas and set the text to “This\rshould\r\not\roverlap”
6. Observe the existing and new text in the Game View
Actual result: “Parse Escape Sequence” is only applied to the newly added text GameObject
Expected result: “Parse Escape Sequence” is applied to all text in the scene
Reproducible with: 2023.1.0a3, 6000.0.70f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a8
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.