Search Issue Tracker
Fixed
Fixed in 6000.3.0a2
Votes
0
Found in
2022.3.61f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
Issue ID
UUM-102246
Regression
No
UI Toolkit Style changes to "*" when UIBuilder is loading Style Classes named using digits
How to reproduce:
1. Open the attached "IN-98390" project
2. Open the UI Builder window
3. In the Assets folder, locate the “GamePage.uxml” Visual Tree Asset and open it inside the UI Builder window
4. Observe the UI Builder window
5. Locate and open the “GamePage.uss” file from the Assets folder in any script editing software
6. Locate the “.1v1_wager” Style Class, rename it to “.onevone_wager”
7. Observe the UI Builder window again
Expected result: UI Style is consistent between different Style Classes
Actual result: VisualElements containing Images have an inconsistent background, UI Buttons break, borders are not respected
Reproducible in: 2022.1.0a5, 2022.3.61f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Could not test in: 2022.1.0a4 (Too many console errors, project does not load correctly)
Reproducible on: macOS 15.3.2 (M1), Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes:
- Similar to https://issuetracker.unity3d.com/issues/ui-builder-resets-visualelement-properties-when-file-path-contains-special-characters but the issue documented there was observed and fixed regarding special characters (not digits or characters)
- Take note of the different Style Classes inside “GamePage.uss”. When the Editor is restarted multiple times in an affected version, the classes containing any digits get renamed to “*”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Add comment