maziggy 0bc98beac5 fix(queue): paginate History with Show more instead of a hard 50-cap (#2682) ...

The Print Queue History tab reported the full count in its header (e.g.
"History (311 items)") but the row builder hard-sliced the list to
items.slice(0, 50) with no control to load the rest, so everything past the
50th finished print was unreachable. The whole history is already loaded
client-side (the queue endpoint has no limit) and sorted -- it just wasn't
drawn.

History now renders progressively: the first page (50) plus a "Show more"
button and a "Showing X of Y" count that loads the next page until the full
list is on screen. The visible count resets to one page only on a deliberate
re-sort or location-filter change -- not on the periodic queue poll, which
produces a fresh array each tick and would otherwise collapse an expanded
view mid-scroll.

Frontend-only; batch grouping and per-row actions unchanged. Two new i18n
keys across all 12 locales. Covered by a test asserting the 50-row cap, the
count label, and that Show more reveals the remainder. Wiki updated.

2026-07-27 12:04:57 +02:00

..

index-D0TAB3FV.js

fix(queue): paginate History with Show more instead of a hard 50-cap (#2682)

2026-07-27 12:04:57 +02:00

index-Di24iyOw.css

fix(queue): paginate History with Show more instead of a hard 50-cap (#2682)

2026-07-27 12:04:57 +02:00