Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.27f1, 6000.0.1f1
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.10f1
2023.3.0b7
6000.0.0b11
Issue ID
UUM-63589
Regression
No
Naming Selectors with improper character combinations in UI Builder logs Errors and has inconsistent indications to Users
Steps to reproduce:
1. Open any Project
2. Navigate to Window > UI Toolkit > UI Builder
3. Save the new USS
4. In the StyleSheets section press the "Add new selector..." text field and type ">" then Return
5. Observe errors printed
6. Then do the same with the character "%" and observe the pop-up message
Actual results: When the user inputs characters ".",">","#","-" to the Selector naming text field "Failed to calculate selector specificity: >" Errors are logged, when inputting "_" or "", the names are valid. But when inputting any other special characters, a pop-up appears that all of these characters can be inputted.
Expected results:* We first present the user with what characters can be inputted, but then when they use them we again fall back to an Error. The Error is the same for all of the characters, so a pop-up in the same style as the first one should be used, to show users a Warning
Reproducible with versions: 2021.3.35f1, 2022.3.20f1, 2023.1.20f1, 2023.2.10f1, 2023.3.0b7
Tested on (OS): macOS Sonoma
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