Search Issue Tracker
Fixed
Fixed in 6000.3.13f1, 6000.5.0b2, 6000.6.X
Votes
0
Found in
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a2
Issue ID
UUM-137536
Regression
No
Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open UI Builder
3. Select "Project" in the "Library" block
4. Expand "Custom Controls (C#)"
5. Expand "UI Test" group
Expected result: All groups are unique and sorted
Actual result: Duplicate group names are present
Reproducible with: 6000.0.71f1, 6000.3.11f1, 6000.4.0f1, 6000.5.0b1, 6000.6.0a1
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Expanding one instance of a group toggles another group with the same name (expanding the first "Group A" toggles the second "Group A", same for the "Group B")
- Group contents are incorrect: "Group A" contains only "Element3" ("Element1" is missing)
- Results may differ if the order of type declarations is changed, indicating potential order-dependent processing or unstable grouping logic
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Nothing happens when entering a converter ID to target property in the Add Binding window when a converter ID was already added and removed
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
Resolution Note:
Fixed in 6000.5.0b2
Resolution Note (fix version 6000.6):
Fixed in 6000.5.0b2
Resolution Note (fix version 6000.3.13f1):
Fixed in 6000.3.13f1