Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.2.0b9
2019.3.0a1
Issue ID
1171103
Regression
No
Ping highlight does not mark a folded child GameObject in the Hierarchy correctly when scrolling is required to reach the object
How to reproduce:
1. Open user-submitted project (WrongPingDraw)
2. Open the 'SampleScene'
3. In the Hierarchy window Unfold the GameObjects 'GRAPHIC INSIDE' and its child 'GameObject (7)'
4. Re-position the 'GRAPHIC INSIDE' GameObject in the Hierarchy so that it is visible in the Hierarchy without scrolling, but child of 'GameObject (7)' named 'GRAPHIC' is not
5. Fold the 'GameObject(7)' and 'GRAPHIC INSIDE' GameObjects
6. Unfold the 'GameObject' object to reveal the 'SLIDER' GameObject
7. Select 'SLIDER' and click on its Target Graphic field to mark 'GRAPHIC'
Expected result: 'GRAPHIC' is highlighted at the correct depth
Actual result: 'GRAPHIC' is highlighted at the wrong depth
8. Fold 'GameObject (7)' and 'GRAPHIC INSIDE' GameObjects
9. Re-position 'GRAPHIC INSIDE' so that it is no longer visible from the top of the Hierarchy without scrolling
10. Select 'SLIDER' and click on its Target Graphic field to mark 'GRAPHIC'
Expected result: 'GRAPHIC' is highlighted
Actual result: 'GRAPHIC' is not highlighted
Reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.11f1, 2019.2.0b10, 2019.3.0a10
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
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a8