Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.1
2020.2
2021.1
2021.1.0a7
Issue ID
1298380
Regression
No
Project Browser Search has slower response when compared to Quick Search and Hierarchy Search
Reproduction steps:
1. Create an empty project
2. Type something into the search of the Project Browser
Expected result: The Search result are returned after the search debouncing threshold specified in the user settings.
Actual result: There's about a 500ms delay before the Search is updated
Reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (fix version 2021.2):
That was made so by design. The search fields in the project browser and the scene hierarchy use a delayed text field and it wait a certain amount of time so you stop typing before showing any results. An option to select the Debounce Threshold (ms) was added in Preferences > Search, available in 2021.2.0a5 and up