Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.6.0a5
Issue ID
UUM-142257
Regression
No
UI Element properties can't be found in Animation window when they don't have a name set
Steps to reproduce:
- Open the "66ETs.zip" project
- Open the "New Animation" Animation Clip
- Select the "NewUXMLTemplate" in Hierarchy
- Press on the "+" icon in the Animation window
- Expand "Panel Renderer"
- Observe the displayed propertiesÂ
Actual results: Only "#Find This" is displayed
Expected results: "#Find This" and "VisualElement" elements are displayed
Reproducible with versions: 6000.6.0a5
Can’t test with versions: 6000.0.75f1, 6000.3.15f1, 6000.4.7f1, 6000.5.0b8, 6000.6.0a4 (No UI Animation Clips)
Tested on (OS): Windows 11 Pro (25H2)
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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.