In v3.23c, the cover preview box was adjusted to fix this bug.
However, I've noticed that since then until the current version - v3.26 - when loading a cover that fills the entire cover preview box, the cover art will crop part of the cover info + checkbox.
Hovering over the cover info field brings it (info field) into view again, but now it's the cover info that will crop part of the cover art (and leave a tiny slit of cover on the left side).
Enabling/disabling "Correct aspect ratio" will reset the behavior; but now it's back to square one (cover art over cover info; hovering reverses field on top)
Here are some screenshots for clarity:
Since this behavior is related to the previous bugfix (I think), and since the OP in that topic could fix that issue with the "Correct aspect ratio" setting, I would like to ask to have the old cover box size/placement restored, or having the cover info position adjusted (move it slightly down) to prevent cropping.
I'm programmatically resizing the cover window just to be sure that it's always square. When implementing this, I did this mainly to protect myself and make sure that even if I'd change the size in the dialog resource by one pixel, it still turns out as being square.
The screenshots clearly show that, on some systems, loading the dialog resource results in a not-at-all square cover window and the programmatic correction adds more than one pixel horizontally.
Even if I can't reproduce this at the moment, I might be able to resize and move the cover info and checkbox in a similar fashion. I'll keep you posted.
By chance I happened to still have the installers for 3.25b and 3.24; and in both (portable installation) I was able to replicate the same behavior on win 10 pro. Later today I should be able to test these in a win 11 system and see if I get the same results as @ohrenkino.
On non-squared covers, the black bars are properly displayed, and "Correct aspect ratio" is working as it should, and not doing anything that it wasn't supposed to do.
So (tentatively) I would call this as "fixed".
@ohrenkino I did end up spending my testing energy and tested v3.26 on my W11 laptop, and I was unable to replicate what you reported. On the exact same (portable) installation where I was getting the bug in W10 I did not get it in W11 on a different machine.