Search Issue Tracker
Fixed
Fixed in 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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment