Search Issue Tracker
Fixed
Fixed in 2022.2.3f1
Won't Fix in 2021.3.X
Votes
3
Found in
2021.3.0f1
2022.1.16f1
2022.2.0b8
2023.1.0a18
Issue ID
UUM-13153
Regression
No
Expose Parse Escape Character
Expose Pase Escape Character through TextElement. (UXML)
Note - Link to the forum where the issue was raised https://forum.unity.com/threads/preventing-escaped-characters-in-textfield.1071425
Comments (3)
-
ChGuidi
Jul 31, 2023 15:10
This is indeed exposed, but if I try it, it doesn't work. It only seems to work starting from 2023.1. Is that the expected outcome of this issue?
-
jsr2k1
May 09, 2023 07:40
This is an important issue because we use file paths in the string fields.
Internally, the path is correct and everything works properly. It is only a visual problem but it is very annoying. -
jsr2k1
May 09, 2023 07:36
I've tested this issue in Unity version v.2022.2.18 and still persists.
- Create a new project
- Create a new script with a public string
- Assign this script to any object in the scene
- Try to write "\\" in the string field
- The second '\' is not visible
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2022.2.3f1):
Fixed in: 2022.2.3f1
Backported solution to expose the property on TextElements.
Resolution Note (2021.3.X):
Backport fix depends on a great number of changes (includes feature work to support this property) present on 2022 onward.