Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131626
Regression
No
Typos in Project Preview Theme helpbox in the UI Toolkit section of Project Settings window
Reproduction steps:
1. Create a new project
2. Edit > Project Settings… > UI Toolkit
3. Observe Project Preview Theme helpbox text
Actual result: “PanelSettings” and “UIDocument” is displayed in the text
Expected result: “Panel Settings” and “UI Document” is displayed in the text
Reproducible with: 6000.4.0b3, 6000.5.0a4
Couldn’t reproduce with: 6000.0.65f1, 6000.3.3f1 (No Project Preview Theme)
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
- Shader Graph does not get saved when pressing 'File -> Save'
- MultiColumnListView does not visually sort the column when BindingSourceSelection is set to "Auto Assign"
- GameObject assigned to Target Graphic in uGUI Toggle component stays dimmed when replacing it if Interactable was toggled off
- "GraphicsBuffer.IsValid()" returns incorrect result when SkinnedMeshRenderer is disabled
- Clear Dynamic Data On Build does not clear data after a clean build when the Atlas Population Mode is set to "Dynamic" or "Dynamic OS"
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.