Search Issue Tracker
Fixed in 3.0.0-preview.6
Votes
0
Found in [Package]
2018.4
2019.4
2020.1.17f1
2020.2
2020.3
2021.1
2021.2
Issue ID
1321890
Regression
No
The search doesn't return any results when searching for settings and entered keyword order doesn't match the original string
How to reproduce:
1. Create a new project
2. Open the Quick Search window
3. In the search field enter 'order script'
4. Observe the Quick Search window
Expected result: The Script Execution Order setting gets returned as a search result
Actual result: The search doesn't return any search results
Reproducible with: Quick Search 1.5.4 (2018.4.33f1), 2.0.2 (2019.4.23f1, 2020.2.7f1, 2020.3.2f1), 3.0.0-preview.5 (2020.2.7f1, 2020.3.2f1), 2021.1.0f1, 2021.2.0a10
Cannot test with: Quick Search 3.0.0-preview.5 (2018.4.33f1, 2019.4.23f1) (the package version is not supported)
Notes:
- The issue is reproducible only while searching for settings
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
- UpdateRendererBonudingVolumes process takes more time when disabled Renderers are used
- "ArgumentNullException: Value cannot be null" error is thrown when selecting a Visual Element with a custom Render Texture set as a background
- Changes are not saved when changing Styles' orders in the UI Builder
- “InvalidOperationException: Not enough space in output buffer (need 24, has 0)” error is thrown when using NativeList.GetVertices()
- High CPU usage when Spline Evaluate functions are used
Resolution Note (fix version 3.0.0-preview.6):
Fixed in 2021.2.0a12
Resolution Note:
Fixed in 2021.1.4f1