Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
1
Found in
2021.2.0a13
2021.2.3f1
2022.1
2022.2
Issue ID
1388196
Regression
Yes
Slider Min and Max Values become the same as the other Slider when selecting multiple Slider GameObjects in the Hierarchy window
How to reproduce:
1. Open the user's attached project "test2021.2.3.zip"
2. In the Hierarchy window select both "Slider" GameObjects under "Canvas"
3. Observe their Min and Max Values in the Inspector window
Expected result: Min and Max Values remain different after selecting multiple Slider GameObjects
Actual result: Min and Max Values become the same as the recently created "Slider (1)" Values
Reproducible with: 2021.2.0a13, 2021.2.8f1, 2022.1.0b4, 2022.2.0a2
Not reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.0a12
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a5
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b10
Resolution Note (fix version 2021.2):
Fixed in 2021.2.14f1