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
- 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
Add comment