Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.5f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-132363
Regression
No
UITK Debugger new Classes element is not created with no information or warnings thrown when adding more than one element with the default name
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open UI Toolkit Debugger (Window > UI Toolkit > Debugger)
- Click on the "Select a panel" dropdown and select "HierarchyWindow"
- Open the "EditorPanelRootElement" foldout
- Open the "VisualElement" foldout
- Select the "Toolbar" element
- Open the "Classes" foldout
- Add a new element by pressing the "+" button
- Repeat step 8
- Observe the Classes list
Actual results: Second element is not added and no information or warnings are thrown
Expected results: Either an informational dialog or a warning is thrown, or the second class is created with an iterated name (for example newStyle 1)
Reproducible with versions: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Tested on (OS): MacOS Silicon Tahoe 26.2
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.