Search Issue Tracker
Fixed
Fixed in 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a2
Votes
0
Found in
6000.0.48f1
6000.1.2f1
6000.2.0a10
6000.3.0a1
Issue ID
UUM-104888
Regression
No
Custom elements not visible in UI Builder when defined in a namespace starting with "Unity"
How to reproduce:
1. Open the “IN-100074_TestUIBuilderNameSpace” project
2. Open Window > UI Toolkit > UI Builder
3. In the Library pane select “Project”
4. Observe available custom elements
Expected result: Custom elements that are defined in a namespace that starts with “Unity” are visible
Actual result: Custom elements that are defined in a namespace that starts with “Unity” are not visible
Reproducible with: 2023.2.0a9, 6000.0.48f1, 6000.1.2f1, 6000.2.0a10
Could not test with: 2022.3.61f1, 2023.2.0a8 ([UxmlElement] attribute is not introduced)
Reproducible on: macOS 15.4.1 (M1 Max)
Not reproducible on: no other environments tested
Notes:
- For reproduction the namespace must start with “Unity”, adding letters in front or using lowercase “u” will not reproduce the behaviour.
- Before version 2023.2.0a9 the “UxmlFactory” pattern is used for creating custom UI Toolkit elements. The behaviour does not reproduce with these attributes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quality Hackweek] Activated Terrain Inspector is active only until the terrain GameObject is deselected when two or more Inspectors are open
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
- ConfigurableJoint's parameters are not saved in the Prefab after Runtime Prefab baking
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
Add comment