Last row in timeline view layout pushes thumbnail off the screen

[forestocean88]

Platform & OS Version
MacOS 10.15.1 and iOS 13.1.3 (both show same issue)

The version of zmNinja you are reporting:
ZMNinjaPro 1.3.082

The version and OS of ZoneMinder you are using:
Zoneminder 1.3.2, Ubuntu Beaver

Device details:
Macbook Pro and iPhone 7

What is the nature of your issue
Bug

Details
The "Timeline" view layout is making the last monitor row taller than the rest, causing the preview image to be pushed off the screen. E.g. if you have 3 monitors, the first two rows are proper height, but the third monitor row's height is larger such that it fills the viewport. This pushes the preview image off the screen, making it necessary to scroll the whole screen to see the image.

See screenshot attached.

Note, this worked fine in the recent past. Two changes may be contributing: I'm sorry I'm not certain which release version broke it, but it was in the last 2-3 releases when this broke. I also went from 3 monitors to 5 monitors recently, so it's conceivable that this is causing the issue, but my hunch is not, since there is plenty of screen real estate below the monitor rows.

This makes using the Timeline more cumbersome than before since one must scroll the whole page each time between the timeline visualization and the thumbnail. When both were visible, it was easy to scrub/hover on the visualization and see the thumbnail without scrolling the whole page.

zmNinja Debug Logs
n/a

Zoneminder Logs (if applicable)
n/a

Web Server Error Logs (if applicable, especially for streaming errors or API error)
n/a

If more info is needed, let me know. I looked at Developer Tools but didn't identify the style causing the layout issue.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you follow the issue template or I may not respond.

[pliablepixels]

could you try this desktop version (mac) https://drive.google.com/file/d/1YXbyg4HtbjcH_lXCq7Z_dQ4cybYlq1FA/view?usp=sharing

[forestocean88]

Confirmed fixed: I ran the version you linked and see that this resolves the issue. Thanks for a very quick turnaround, great!