There is currently a merge request at <https://gitlab.com/mailman/django-mailman3/-/merge_requests/345> to hide the "Results per page:" dropdown from some Postorius and HyperKitty pages when the full list of items (lists) is on the page.
I.e. when the number of items is <=10 and the "Results per page:" is the default 10, don't display the dropdown. However there is some controversy over whether this should also apply say when the number of items is > 10 but still is on one page.
So the question is if we are going to hide the dropdown when "Results per page:" is the default 10 and there are <= 10 items so all are on the page, should we also hide it when say "Results per page:" is 25 and there are 22 items all on the page. Your opinion on this is requested via a reply in this thread.
See the merge request (link above) for arguments pro and con.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
For any setting N items per page, if actualy number of items is less than or equal to N, no need to render, no need for dropdown. Don't show it.
If someone is trying to scrap the output for other purposes, perhaps you can give them an alternative JSON output for that, or something easler to parse. Or at the very least add an HTML comment with metadata (like "<!-- total_items=X, page=Y, total_pages=Z -->").
JP
-- How do they get deer to cross the road only at those yellow road signs?
Have a great day and don't forget to laugh!
http://www.gcfl.net (The Good, Clean Funnies List): Good, clean daily funnies you can safely tell your Mom!
On Sat, Mar 07, 2026 at 11:51:43AM -0800, Mark Sapiro wrote:
There is currently a merge request at <https://gitlab.com/mailman/django-mailman3/-/merge_requests/345> to hide the "Results per page:" dropdown from some Postorius and HyperKitty pages when the full list of items (lists) is on the page.
I.e. when the number of items is <=10 and the "Results per page:" is the default 10, don't display the dropdown. However there is some controversy over whether this should also apply say when the number of items is > 10 but still is on one page.
So the question is if we are going to hide the dropdown when "Results per page:" is the default 10 and there are <= 10 items so all are on the page, should we also hide it when say "Results per page:" is 25 and there are 22 items all on the page. Your opinion on this is requested via a reply in this thread.
See the merge request (link above) for arguments pro and con.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to jp_mailman@gcfl.net
John Price wrote:
For any setting N items per page, if actualy number of items is less than or equal to N, no need to render, no need for dropdown. Don't show it.
Wouldn't that result in a situation where you can use the dropdown to show more entries, but would often not be able go back to show less entries, as the dropdown won't be displayed?
For example, if the list has 175 entries and 25 are shown. You would be able to switch the display to show 200 entries, but then you can't go back to 100 or 50 entries if 200 are too much for you, as the dropdown is not shown any longer (because all 175 entries fit on one page that will show up to 200 entrues).
-thh
On 3/7/26 15:42, Thomas Hochstein wrote:
John Price wrote:
For any setting N items per page, if actualy number of items is less than or equal to N, no need to render, no need for dropdown. Don't show it.
Wouldn't that result in a situation where you can use the dropdown to show more entries, but would often not be able go back to show less entries, as the dropdown won't be displayed?
That's the main argument against it. The counter argument is you can use the browser's back button or refetch the URL without the count= fragment, but there is concern that there could be circumstances where that doesn't work.
For example, if the list has 175 entries and 25 are shown. You would be able to switch the display to show 200 entries, but then you can't go back to 100 or 50 entries if 200 are too much for you, as the dropdown is not shown any longer (because all 175 entries fit on one page that will show up to 200 entrues).
How significant an issue do you think that is?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Mar 07, 2026 at 05:00:43PM -0800, Mark Sapiro wrote:
On 3/7/26 15:42, Thomas Hochstein wrote:
John Price wrote:
For any setting N items per page, if actualy number of items is less than or equal to N, no need to render, no need for dropdown. Don't show it.
Wouldn't that result in a situation where you can use the dropdown to show more entries, but would often not be able go back to show less entries, as the dropdown won't be displayed?
That's the main argument against it. The counter argument is you can use the browser's back button or refetch the URL without the count= fragment, but there is concern that there could be circumstances where that doesn't work.
I see now what the problem is and Thomas has changed my mind. Always show pulldown. It's janky to have to use the back button after changing the number per page larger, and it goes away. No one wants janky. :)
-- "All of the people in my building are insane. The guy above me designs synthetic hairballs for ceramic cats. The lady across the hall tried to rob a department store... with a pricing gun... She said, "Give me all of the money in the vault, or I'm marking down everything in the store..."
Have a great day and don't forget to laugh!
http://www.gcfl.net (The Good, Clean Funnies List): Good, clean daily funnies you can safely tell your Mom!
Mark Sapiro writes:
How significant an issue do you think that is?
Very, if you have 20K lists. Hacked the code to allow you to get all of them, which took forever to load but also was *way* faster to scan by eye, or search with Ctrl-F for that matter, if you weren't quite sure of a search term. The use case was that a lot of those lists were sequenced (eg, "commits-2022", "commits-2023"). They couldn't remember the "commits" part, but once they found it paged mode refreshed a lot faster as they made the changes they wanted to multiple lists.
Not my problem anymore (and it won't be theirs in this decade, QA/Security is really tightass there and they have the "unlimited page length" patch they need), but that use case does exist.
Not sure what harm the extra information does. If it seems distracting or ugly where it is, maybe it can be relocated to someplace on the page where that's less so but you can still find it if you need it.
I would be more in favor of a larger default (25 or 50, even 100), although I live in a bandwidth-rich country. Maybe that's not feasible in many places.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
On 9/03/2026 4:18 am, Stephen J. Turnbull wrote:
Mark Sapiro writes:
How significant an issue do you think that is?
I would be more in favor of a larger default (25 or 50, even 100), although I live in a bandwidth-rich country. Maybe that's not feasible in many places.
I would like to be able to set the default number of lists, we run 13 and its annoying to always have to use the drop down to see the extra 3 lists.
Many thanks for a brilliant program guys
On 3/8/26 10:18, Stephen J. Turnbull wrote:
Mark Sapiro writes:
How significant an issue do you think that is?
Very, if you have 20K lists.
That's not the issue I was asking about. That issue is if the selection dropdown is hidden from any page that shows all the items, then in the case where there are say 35 items and the default 10 per page shows the first of 4 pages and you select 50 per page from the dropdown then all 35 are on a page with no dropdown, and since there is no dropdown you can't easily go back to a fewer number per page, at least if the browsers back button won't do it for some reason.
Also, the issue isn't always the number of lists. Consider <https://lists.mailman3.org/mailman3/lists/?all-lists> which shows only 2 (or 4 if you can see the hidden ones) lists, but even so, <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/latest> has over 2500 threads. This is relevant because, currently at least, pagination is done in a common django_mailman3 meth and any change will apply globally.
I would be more in favor of a larger default (25 or 50, even 100), although I live in a bandwidth-rich country. Maybe that's not feasible in many places. Maybe we need another issue/MR to configure the default number of items per page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
On 3/8/26 10:18, Stephen J. Turnbull wrote:
Mark Sapiro writes:
How significant an issue do you think that is?
Very, if you have 20K lists.
That's not the issue I was asking about. That issue is if the selection
The point is a user story where it was important to be able to narrow the window conveniently.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
participants (5)
-
John Price -
Mark Sapiro -
Phil -
Stephen J. Turnbull -
Thomas Hochstein