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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- 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
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