Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
6000.0.48f1
6000.1.2f1
6000.2.0a10
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
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
- "GetPreferedValue" returns max value when using auto-sizing
Add comment