Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.2.15f1
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-129782
Regression
No
Location tooltip in the Viewport of UI Builder window does not update when the UI Document Asset is moved to a different location
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Create a new UI Document Asset (Assets > Create > UI Toolkit > UI Document)
- Double click the created UI Document in the Project Browser to open the UI Builder window
- Dock the UI Builder window
- Drag and drop the UI Document into the "Assets/Scenes" folder
- Hover the mouse cursor over the "NewUXMLTemplate.uxml" label in the Viewport
- Observe the tooltip
Actual results: The tooltip still shows that the UI Document is located in the Assets folder
Expected results: The tooltip shows that the UI Document is located in the Scenes folder
Reproducible with versions: 6000.0.64f1, 6000.2.15f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Tested on (OS): MacOS M1 Silicon Tahoe 26.0.1
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
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.