Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131726
Regression
No
VisualTreeAsset Inspector button text includes period symbol
Reproduction steps:
1. Create a new project
2. Edit > Project Settings… > UI Toolkit
3. Enable Hierarchy Integration
4. Create UI Document GameObject in the Hierarchy
5. Select newly created GameObject and attach Source Asset in the Inspector
6. Select UI Document child GameObject in the Hierarchy and observe the button in the Inspector
Actual result: Period symbol is displayed at the end of the button text
Expected result: Period symbol is not displayed at the end of the button text
Reproducible with: 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Couldn’t reproduce with: 6000.0.65f1 (No Hierarchy Integration)
Reproduced on: macOS Tahoe 26.2 (M4)
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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.