Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a11
2019.2.0a1
Issue ID
1131012
Regression
Yes
Selection of the array elements in the Inspector is offset when beginning of the array was hidden using the slider
How to reproduce:
1. Open attached project "Case_1131012_repro.zip"
2. Select "ArrayObject" GameObject in the hierarchy
3. In the Inspector, scroll down, so some of the array elements, in the beginning, are not visible
4. Click on the any of the fields of the elements
Expected result: Field, which is behind the mouse cursor is selected
Actual result: Selected field is not the one which is behind the mouse cursor
Reproducible with - 2019.1.0a11, 2019.1.0b5, 2019.2.0a6
Not reproducible with - 2017.4.21f1, 2018.3.7f1, 2019.1.0a10
Notes: Offset is determined by how many elements at the beginning of the array are hidden. If X elements are hidden, selection will be offset by X.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0a9