Search Issue Tracker
By Design
Votes
0
Found in
2021.2
2022.1
2022.1.0b11
2022.2
Issue ID
1413713
Regression
No
The Save button is not disabled when saving Search Query as an Asset with only a Space in the Name field
To reproduce:
1. Download the attached project "Search.zip" and open it in Unity
2. Open the Search window
3. Type something in the Input Field of Search window (in example "t: texture")
4. Press the Save button > Save Project...
5. In opened window delete entered name
6. Observe that the "Save" button is disabled
7. Enter a Space in the name input field
Expected Result: The "Save" button is still disabled
Actual Result: The "Save" button becomes active, you can press it and upon that it produces Errors in the Console:
"'Assets/ .asset' is not a valid asset file name.
UnityEditor.GenericMenu:CatchMenu (object,string[],int)"
"Failed to save search query at Assets/ .asset
UnityEditor.GenericMenu:CatchMenu (object,string[],int) (at /Users/bokken/buildslave/unity/build/Editor/Mono/GUI/GenericMenu.cs:127)"
Reproduced on Unity 2021.2.18f1, 2022.1.0b14 and 2022.2.0a9
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2022.2.X):
After some investigation, the save button in OSX cannot be disabled if there's only an empty space. Therefore if the user continues to save the current query, then the system detects the invalid file name and reports the error in the console which is correct.