Search Issue Tracker
Fixed
Fixed in 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.53f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
6000.4.0a1
6000.5.0a1
Issue ID
UUM-111885
Regression
No
Search results number in Saved Searches Panel is not properly visible when Search query is selected in light Editor mode
Steps to reproduce:
1. Create a new project and make sure that Light Editor mode is selected
2. Open Search window (Window > Search > New Window)
3. Enter something in a search bar that would show over 1000 results (eg. “e”)
4. Press Save button and select “Save User” option
5. Click on saved Search query in Saved Searches Panel and observe
Actual results: Search results number is barely visible
Expected results: Search results number clearly visible
Reproducible with versions: 2022.2.0a19, 6000.0.53f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Not reproducible with versions: 2021.3.54f1, 2022.3.64f1
Tested on (OS): Windows 11, macOS Sequoia 15.4 (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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 6000.4.0b4):
Fixed in 6000.4.0b4
Resolution Note (fix version 6000.3.4f1):
Fixed in 6000.3.4f1
Resolution Note (6000.0.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.