Search Issue Tracker
Fixed
Fixed in 2022.3.X, 2022.3.6f1
Votes
0
Found in
2022.3.5f1
Issue ID
UUM-49340
Regression
Yes
Parse escape characters are not ignored when used in UI Toolkit TextField
Reproduction steps:
1. Open the attached project “ParseEscape”
2. Open the “Assets/Scenes/SampleScene” Scene
3. Enter the Play Mode
4. Select the TextField in the Game view
5. Type “\\1” in the TextField
Expected result: The TextField shows “\\1”
Actual result: The TextField shows “\1\”
Reproducible with: 2022.2.0a14, 2022.3.5f1
Not reproducible with: 2021.3.30f1, 2022.2.0a13, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6
Fixed in: 2022.3.6f1
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: The behavior on 2022.2.0a13 didn’t match the fixed version behavior, and it only hides the second '\' character
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment