Sketchbook view scroll position reverts if selected item off screen

[Jeff-Haas]

Describe the problem

If an item is selected in the "Sketchbook view and the view is scrolled until that item goes off screen, the scroll jumps back to bring the selected item into visibility if the mouse pointer is over the view.

To reproduce

1. If you don't already, create enough sketches in the sketchbook to make the "Sketchbook" view scrollable.
   ⓘ You can reduce the necessary number of sketches by resizing the IDE window to the minimum vertical size.
2. Click the folder icon on the Activity Bar to open the Sketchbook view.
3. Click on any item in the view that can be scrolled off screen.
   
4. Drag the scroll bar until the selected item is off screen.
5. Move the mouse pointer over the Sketchbook view.
   🐛 The view jumps pack to the scroll position that makes the selected item visible.
6. Use the mouse wheel to scroll the Sketchbook view until the selected item is off screen.
   🐛 The view jumps pack to the scroll position that makes the selected item visible.

Expected behavior

You are able to scroll farther down the list and then click what you are interested in. You should be able to scroll what you selected up out of sight.

Arduino IDE version

76f9f63

Operating system

Windows

Operating system version

10

Additional context

This behavior is not obvious and you can keep scrolling for a few moments until you realize you are getting nowhere.

---

You can scroll using the arrow keys, but this moves the highlight down the list of files, which is different behavior.

---

The Boards Manager and Library Manager views do not have this problem (possibly because their contents are not selectable in the same way as the Sketchbook view.

---

Additional reports:

• Unable to select files in explorer tab in Arduino ide2.0.3 #1891
• Jumpin drop down menue in v2.0.3 #1900
• https://forum.arduino.cc/t/sketchbook-folder-depth/1068392/4
• https://forum.arduino.cc/t/sketchbook-folder-depth/1068392/6

Issue checklist

• I searched for previous reports in the issue tracker
• I verified the problem still occurs when using the latest nightly build
• My report contains all necessary details