Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.8f1
6000.4.0b8
6000.5.0a6
Issue ID
UUM-134017
Regression
No
UI Builder adds non-removable built-in class selectors when adding a custom selector via “Add Selector...”
Steps to reproduce:
- Create a new project using Universal 3D template
- Go to Assets > Create > UI Toolkit > UI Document (UXML)
- Open the created UI Document in UI Builder
- Add any element to Hierarchy, e.g. "Toggle"
- Right-click on it and select "Add Selector..."
- In the selector field, type in any name (e.g. ".test") and click enter
- Click on the previously created element ("Toggle") and observe its Style Class List in Inspector
Actual results: "Toggle" elements has ".unity-toggle" selector in the Style Class List and it is not removable
Expected results: "Toggle" elements has ".test" selector in the Style Class List and it is removable
Reproducible with versions: 6000.0.66f1, 6000.3.8f1, 6000.4.0b8, 6000.5.0a6
Tested on (OS): Ubuntu 24.04, Windows 11
Note:
- Reproduces across multiple UI Toolkit controls, not limited to Toggle
- The built-in class appears to override or replace the custom selector added via “Add Selector...” and cannot be removed from the Style Class List
Add comment
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
Resolution Note:
No "non-removable" classes are added by the UI Builder. They are part of those controls. They are non-removable because data that is not part of the current UXML asset being authored cannot be changed. Those classes are added after the UXML has been loaded.
Resolution Note (6000.5.X):
No "non-removable" classes are added by the UI Builder. They are part of those controls. They are non-removable because data that is not part of the current UXML asset being authored cannot be changed. Those classes are added after the UXML has been loaded.