Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.18f1
2022.2.0a8
2023.1.0b8
2023.2.0a6
Issue ID
UUM-27864
Regression
No
Text containing "\u" and "\U" is incorrectly displayed when using UIElements Label or TextField
How to reproduce:
1. Open the attached user project “UIToolkitEscapeSequenceParsing.zip“
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Enter Play Mode
Expected result: Text is displayed correctly
Actual result: Square symbols appear in the text
Reproducible with: 2021.3.18f1, 2022.2.0a8
Not reproducible with: 2022.2.0a9, 2022.2.6f1, 2023.1.0b3, 2023.2.0a2
Can’t test with: 2020.3.45f1 (Errors in the Console)
Reproduced on: macOS 13.0.1 (Intel)
Note:
- Issue is reproducible in Builds (although instead of a square symbol, nothing is shown)
- If at least three characters follow a "\u" and they do not form a valid unicode escape sequence then the entire sequence will be replaced with the "square" unicode character
- If at least seven characters follow a "\U" and they do not form a valid unicode escape sequence then the entire sequence will be replaced with the "square" unicode character
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
The code's changed significantly since 2021.3, so we can't backport the bugfix. Please update to version 2022.2 or later.
Resolution Note (2023.2.X):
The code's changed significantly since 2021.3, so we can't backport the bugfix. Please update to version 2022.2 or later.