Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.25f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1348825
Regression
No
Project Browser slider doesn't get reset after selecting any item in Favorites hierarchy and clearing the search bar
How to reproduce:
1. Create a new project
2. Set the Project window slider to a non-default value (e.g. highest value)
3. Type 't:scene' into the search bar of the Project Window
4. Save the search and call it 'Test' (it should appear in the 'Favorites' hierarchy)
5. Select any folder under 'Assets' in the Project Window hierarchy
6. Set the Project window slider to a non-default value (e.g. lowest left)
7. Select the 'Test' search in the Favorites hierarchy (the slider value should return to the value set in step 2)
8. Change the value of the search bar from 't:scene' to any string
9. Observe the slider.
Expected result: The slider returns to the same value that was set in step 6
Actual result: The slider value doesn't change
Reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.14f1, 2021.2.0b3, 2022.1.0a2
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a7
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.4f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.25f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.34f1