Jellyfin-web: Live TV display in web GUI lacks pagination

[dinki]

This is minor but thought I'd report it.

The Live TV display of upcoming Movies and Shows in the web GUI lacks pagination and only the first page is shown. This can be reviewed by clicking on:

Live TV->Programs->Movies
or
Live TV->Programs->Shows

Expected behavior would be to show all items separated by page with page navigation at top, bottom or both.

[dinki]

I think this is actually a bug as the only what would be on the first page is shown rather than the entire movie/show list. For example, the shows will only upcoming shows that start with A-C but there's no way to see the shows that may start with D-Z

[dinki]

I tried tackling this myself but failed. I did discover that the files used are:

https://github.com/jellyfin/jellyfin/blob/21a8d273782a1a71678131f17ebaafd2b997f286/MediaBrowser.WebDashboard/dashboard-ui/livetv.html

Around lines 22-30 for TV Episodes and lines 31-39 for TV movies. It then passes information to:

https://github.com/jellyfin/jellyfin/blob/21a8d273782a1a71678131f17ebaafd2b997f286/MediaBrowser.WebDashboard/dashboard-ui/list/list.html

Somewhere in there the pagination needs to be added. You can see an example of what the pagination looks like by viewing:

https://github.com/jellyfin/jellyfin/blob/21a8d273782a1a71678131f17ebaafd2b997f286/MediaBrowser.WebDashboard/dashboard-ui/movies.html

Which I _THINK_ uses the <div class="paging"></div> code for setting things up.

Again, I'm just trying to sort through all this and would certainly like some help deciphering this. Perhaps if I can see how this is done I can help with other web ui tasks. Thanks

[dinki]

Posting again that this should be labeled a bug and not a feature request.

[PrplHaz4]

I have confirmed this bug is still present for me in 10.3.2

[stale[bot]]

Issues go stale after 60d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 7d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

[dinki]

bump. Still needs to be fixed

[stale[bot]]

Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

[MrTimscampi]

Looking into this, it's because this page is treated as a suggestion page.

As such, it only gets a few items (9 or 12 -or 14? For some reason it adds 2 more when it's 12 items-).

It would be trivial to make it respect the page limit settings, but adding proper pagination would be a bit more involved,

[MrTimscampi]

As this is a feature request and not a bug, please redirect this to https://features.jellyfin.org/

[dinki]

I disagree. The user is only able to see the first page. In my case, only programs that start with a numeric or the letter 'a' are shown. Anything 'b-z' is not accessible.

While I understand that live tv is not a big priority for most it does not change the fact that this is indeed a bug.

[MrTimscampi]

This has nothing to do with Live TV being a priority or not.

The page is a suggestions page and not a library one. We currently don't support pagination on suggestion pages, so this is a feature and not a bug. As such, it goes on https://features.jellyfin.org/

We are cleaning up issues because we have/had a lot of feature requests and suggestions among legitimate issues, making it hard to track what is REALLY an issue for people.

[DMouse10462]

I think there's a distinction to be made between "operating as expected" from a written code standpoint vs. a UI/UX standpoint. This is a frontend application, and I would expect that a frontend application treats design and implementation inconsistencies as bugs from a UI/UX standpoint because the view (a list of all programs listed as Movies/TV Shows) is expected (based on the other cardviews) to do something (list all of its contents with pagination/lazy loading/etc.) that isn't happening. The code may be operating as expected from what you see in the .js file, but a user looking at the view would argue otherwise.

In a user interface, not providing the necessary UI in a consistent manner is, in my argument, a bug.