[GH-ISSUE #2339] Message Log not loading additional messages on high resolutions #1575

New issue

Closed

opened 2026-02-27 11:17:53 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 11:17:53 +03:00

Owner

Originally created by @PatTheMav on GitHub (Aug 7, 2021).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/2339

Impacted versions

OS Type: Debian
OS Version: 10
Database Type: PostgreSQL
Database version: 11.12
Modoboa: 1.17.0
installer used: No ?
Webserver: Nginx

Steps to reproduce

Open Modoboa's web interface on a high resolution screen (e.g. 4k or 5k)
Open Message Log
See Message log displaying a first set of messages, but not loading additional ones

Current behavior

I originally reported that the message log is not populated, but that turned out to not be correct. Instead it seems that if the browser window is big enough to display the initial set of logged messages in the Message Log, no scroll event can happen and no additional messages are loaded.

Thus it appears as if only the first few events since an upgrade to 1.16 are contained in the log. But when resizing the browser window to require scrolling to get to the bottom of the list, additional messages are loaded.

(Do note that this is quite probably a bug in the web interface and should thus be moved into that repo).

Expected behavior

Additional messages are loaded even on screen resolutions where the initial page does not require scrolling.

Originally created by @PatTheMav on GitHub (Aug 7, 2021). Original GitHub issue: https://github.com/modoboa/modoboa/issues/2339 # Impacted versions * OS Type: Debian * OS Version: 10 * Database Type: PostgreSQL * Database version: 11.12 * Modoboa: 1.17.0 * installer used: No ? * Webserver: Nginx # Steps to reproduce * Open Modoboa's web interface on a high resolution screen (e.g. 4k or 5k) * Open Message Log * See Message log displaying a first set of messages, but not loading additional ones # Current behavior I originally reported that the message log is not populated, but that turned out to not be correct. Instead it seems that if the browser window is big enough to display the initial set of logged messages in the Message Log, no scroll event can happen and no additional messages are loaded. Thus it appears as if only the first few events since an upgrade to 1.16 are contained in the log. But when resizing the browser window to require scrolling to get to the bottom of the list, additional messages are loaded. (Do note that this is quite probably a bug in the web interface and should thus be moved into that repo). # Expected behavior Additional messages are loaded even on screen resolutions where the initial page does not require scrolling.

kerem

2026-02-27 11:17:53 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 11:17:54 +03:00

Author

Owner

@stale[bot] commented on GitHub (Oct 8, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 8, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kerem commented

2026-02-27 11:17:54 +03:00

Author

Owner

@tonioo commented on GitHub (Oct 14, 2021):

@PatTheMav This is a general bug we have with the "infinite scroll" feature which behaves badly on high resolutions. I don't think I'll fix it because we won't use such mode in the new interface.

@tonioo commented on GitHub (Oct 14, 2021): @PatTheMav This is a general bug we have with the "infinite scroll" feature which behaves badly on high resolutions. I don't think I'll fix it because we won't use such mode in the new interface.

kerem commented

2026-02-27 11:17:54 +03:00

Author

Owner

@ksaadDE commented on GitHub (Jun 27, 2022):

@PatTheMav I don't think I'll fix it because we won't use such mode in the new interface.

#closed?

@ksaadDE commented on GitHub (Jun 27, 2022): > @PatTheMav I don't think I'll fix it because we won't use such mode in the new interface. #closed?