Search Issue Tracker
By Design
Votes
0
Found in
2017.4.11f1
Issue ID
1085819
Regression
No
"GUILayout.BeginScrollView" incorrectly clamps the scroll position value
Reproduction steps:
1. Open "Project Search Pro.zip" project
2. Press "Ctrl" + "K"
3. Write "Om"
4. Press the "Up" or "Down" Arrow once
Expected Result: The window scrolls to the last element as to show it fully
Actual Result: The window scrolls to the last element, but doesn't fully show it
Reproduced with: 2019.1.0a6, 2018.3.0b8, 2018.2.14f1, 2018.1.9f2, 2017.4.14f1
Note:
Works with the scroll wheel
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
The problem must be fixed in user code. I've answered the user directly, but the gist of it is that when skipping IMGUI controls to avoid conflicting events, one must make sure that they still appear in the layout and get their control IDs allocated.