Closed
Description
Describe the problem
When the mouse pointer is hovered over one of the Library/Boards Manager or list items, a version menu and "INSTALL" button are added at the bottom of the item, which increases its vertical size.
🐛 When the length of the listings fits within the vertical dimension of the view when not hovered, but does not fit when hovered, some glitches can occur.
To reproduce
- Open the "Library Manager" view.
- Resize the horizontal width of the view to the minimum.
ⓘ This is the width set by the IDE by default. - Type
arduinoiotcloud
in the "Filter your search..." field.
ⓘ This is only an arbitrary example of a search that produces a suitable length of listings. By chance it has the perfect length for the default window and view dimensions on my machine. - Resize the vertical dimension of the Arduino IDE window so that it is just long enough to show the full listings while in the non-hovered state, without a scrollbar on the Library Manager view.
- ❗ Without passing the mouse pointer over any of the other library listings in the view along the way ❗, move the mouse pointer from an area of the Arduino IDE window outside the "Library Manager" view to hover the mouse pointer over "Arduino_ConnectionHandler", .
🐛 Only half the "INSTALL" button is shown:
- ❗ Without passing the mouse pointer over any of the other library listings in the view along the way ❗, move the mouse pointer from an area of the Arduino IDE window outside the "Library Manager" view to hover the mouse pointer over "ArduinoIoTCloud", .
🐛 The "INSTALL" button is not shown:
Arduino IDE version
2.0.0-rc9.3
Operating system
Windows 10
Additional context
The issue was introduced by #1385 (does not occur when using the build from df3a34e)
The reason why the issue only occurs with the view at or near the minimum width seems to be related to the fact that, at this width, the position of the "INSTALL" button is below the version menu:
While at any greater width it is to the side of the version menu:
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