Search Issue Tracker
Fixed
Won't Fix in 6000.3.X, 6000.4.X
Fixed in 6000.5.0a5
Votes
0
Found in
6000.3.0b10
6000.4.0a5
6000.5.0a1
Issue ID
UUM-127032
Regression
No
Allowing spaces in the "Category" field creates empty categories in the Shader Graph Templates window
Steps to reproduce:
- Create a project (Universal 2D)
- Go to the "Project" window
- Click "Create" -> Shader Graph -> From Template...
- Select "Empty Shader Graph" and click "Create"
- Select the newly created graph in the "Project" window
- Go to the "Inspector" section
- Check "Use As Template"
- Add graph name, description, icon, and thumbnail
- In the "Category" field, add several spaces
- Save all the changes
- Click "Create" -> Shader Graph -> From Template...
- Observe how the"Category" is displayed in the template window
Actual results: The Category section is empty in the template window
Expected results: Validation for spaces should be added
Reproducible with versions: 17.5.0 (6000.5.0a1) 17.3.0 (6000.4.0a5), 17.4.0(6000.3.0b10)
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): macOS - Tahoe 26.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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note (6000.4.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.
Resolution Note (6000.3.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.