Search Issue Tracker
Fixed in 2021.3.36f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0b2
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b13
2023.3.0a9
Issue ID
UUM-52935
Regression
Yes
GameObjects selection order cycles from the bottom rendered element to the top rendered element when selecting UI GameObjects in the Scene window
How to reproduce:
1. Open the user’s attached “U.1673155.zip” project
2. Open the Scene window and left-click a few times on a slider’s marker
3. Observe the Hierarchy window
Expected result: “Slider” GameObject is selected first, and then selection cycles from the top rendered element to the bottom rendered element
Actual result: “Canvas” or “Panel” GameObject is selected first, and then selection cycles from the bottom rendered element to the top rendered element
Reproducible with: 2021.2.0a19, 2021.2.19f1, 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b13, 2023.3.0a9
Not reproducible with: 2021.2.0a18
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.3):
Fixed in: 2023.3.0b2
Resolution Note (fix version 2023.2):
Fixed in: 2023.2.8f1
Resolution Note (fix version 2022.3):
Fixed in: 2022.3.19f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.36f1