Selected option in combo box is not always fully in view

Selected option in combo box is not always fully in view. In the example the selected option (highlighted in yellow) can end up almost completely out of view when navigating through the options of the combo box.

1. Open the editor
2. Create a new widget blueprint
3. Add a combo box to the designer tab
4. Add 9 default options
5. Name the options Test1 -Test9
6. Set the max list height to be 70
7. Save and compile
8. Open the level blueprint
9. Add the widget to the viewport on begin play
10. Play in Editor
11. Click the combo box
12. Make a selection (combo box will close(expected))
13. Open the combo box again (an option should be highlighted in yellow)
14. Use the arrow keys on the key board to navigate down through the list of options
15. Notice that at certain points the selected option is not fully in view

Expected: Any option that is selected could be fully in view
Result: The selected option (highlighted in yellow) can end up almost completely out of view

How does TextureRenderTarget2D get TArray<uint8> type data?

Why does the REMOVE method of map container remove elements have memory leaks?

How do I set a material as a post-processing material?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

UMG RichText not appear image when packaged

How to delete some elements correctly when deleting an array loop?

What is the difference between Camera and CineCamera?

In UE5.4, custom variables in the level blueprint cannot be set to default values, and the eyedropper tool is also unavailable, whereas in UE4.27, these features work normally.