Infinite scroll / remove pagination

[joshua4 12]

This has been a requested feature for some time. When are we going to have a setting for it? I do not want to click arrows or page numbers. I also do not want to "hack" javascript files.

Edited November 29, 2018 by joshua4

[Luke 42078]

I'm hoping to be able to spend more time on it after the 3.6 release. Thanks.

[Happy2Play 9780]

It was already tried in beta 3.6 and there were to many complaints about page load times.  Items still have to be restricted in order to load the page.  On the beta you can still see the issue on some pages that load all items like selecting specific genres.  But I am sure Luke will come up with a lazy load solution.

[Luke 42078]

It was already tried in beta 3.6 and there were to many complaints about page load times.  Items still have to be restricted in order to load the page.  On the beta you can still see the issue on some pages that load all items like selecting specific genres.  But I am sure Luke will come up with a lazy load solution.

 

No, it wasn't tried. That was just a build or two when it was just rendering all results, which is not what he's requesting here.

[Happy2Play 9780]

No, it wasn't tried. That was just a build or two when it was just rendering all results, which is not what he's requesting here.

 

Right just like the Hack loads every item at one.  Realistically can't be done without long load times.

 

So a infinite scroll that still only loads x amount of items at once.  Because without a item limit you will always have long load times for people with large libraries.

Edited November 29, 2018 by Happy2Play

[joshua4 12]

It was already tried in beta 3.6 and there were to many complaints about page load times.  Items still have to be restricted in order to load the page.  On the beta you can still see the issue on some pages that load all items like selecting specific genres.  But I am sure Luke will come up with a lazy load solution.

 

Infinite scroll is completely possible without impacting page load time.

[SikSlayer 249]

I guess the solution Luke would have in mind would be to load the next 'page' worth of content when you scroll to the end... there's been many examples of that (none come to mind ATM but...   )

Edited November 29, 2018 by SikSlayer

[Luke 42078]

Correct.

[Asturaetus 4]

I guess the solution Luke would have in mind would be to load the next 'page' worth of content when you scroll to the end... there's been many examples of that (none come to mind ATM but...   )

Oh god I hope this feature never comes. Having to scroll to the bottom of the page god knows how many times to get to the end of the library? That would be a horrendous user experience and a deffinitive criteria to immediately deinstall emby and never use it again.

[Happy2Play 9780]

Oh god I hope this feature never comes. Having to scroll to the bottom of the page god knows how many times to get to the end of the library? That would be a horrendous user experience and a deffinitive criteria to immediately deinstall emby and never use it again.

 

Obviously you haven't seen how many users have been requesting this for years.

[joshua4 12]

Oh god I hope this feature never comes. Having to scroll to the bottom of the page god knows how many times to get to the end of the library? That would be a horrendous user experience and a deffinitive criteria to immediately deinstall emby and never use it again.

 

What is at the bottom of the page you want to see?

[Asturaetus 4]

What is at the bottom of the page you want to see?

What do you mean? The next subset of items in the library of course. If I opening a library only loads lets say the first 100 entries and I had to scroll down for it to load the next set of 100 - I would have to scroll down 20 times to reach the end of at least one of my libraries.

Edited November 30, 2018 by Asturaetus

[ebr 16183]

What do you mean? The next subset of items in the library of course. If I opening a library only loads lets say the first 100 entries and I had to scroll down for it to load the next set of 100 - I would have to scroll down 20 times to reach the end of at least one of my libraries.

 

Or you could search or use the letter jump or sort your library so that what you are looking for is at the top...

[joshua4 12]

What do you mean? The next subset of items in the library of course. If I opening a library only loads lets say the first 100 entries and I had to scroll down for it to load the next set of 100 - I would have to scroll down 20 times to reach the end of at least one of my libraries.

 

The amount of effort is the same as clicking pagination 20 times. I'm not seeing what is so troubling for you.

[Luke 42078]

Yes it will be a better experience when all is said and done.

[Asturaetus 4]

The amount of effort is the same as clicking pagination 20 times. I'm not seeing what is so troubling for you.

Eh no - it is a difference in time to just make for example a few clicks in quick succession where emby doesn't even have to load everything or to scroll down. All sites I know that use this feature need a considerably longer time to navigate then sites that either load everything at once or separate the content into pages.

 

 

Or you could search or use the letter jump or sort your library so that what you are looking for is at the top...

That's ok if you know the content by name. But not if you only know for example the poster or the general position in the library. That's also a thing where pages come in useful because they are a form of orientation. I for example know that one entry is somewhere on site 8 or 9 or the posters of content in its vicinity.

 

And with infinite scrolling/lazy loading there is usually no way to quickly navigate to certain positions in a library - let's say the halfway point - because the scroll bar does not represent the actual scrolling position because as soon as new content is loaded the position on the scrollbar moves up.

Edited November 30, 2018 by Asturaetus

[Luke 42078]

It won't be like that at all, where you reach the bottom and have to wait for a loading spinner. The recycling will be happening continuously as you scroll so i don't think it will be noticed too much.

[Asturaetus 4]

It won't be like that at all, where you reach the bottom and have to wait for a loading spinner. The recycling will be happening continuously as you scroll so i don't think it will be noticed too much.

Then it wouldn't be all that bad - but I think some form of scrollindicator (a bar or percentage) to give a general orientation where in relation to the libary size you currently are would probably be something to consider. (because like I said the scroll bar of the browser is usually a very poor indicator.)

Edited November 30, 2018 by Asturaetus

[ebr 16183]

Apple, Roku, Android TV and Fire TV all already do this so I think you find it useful once implemented.

[joshua4 12]

Apple, Roku, Android TV and Fire TV all already do this so I think you find it useful once implemented.

 

Except Netflix. They prefer their annoying as hell carousels. 

[ebr 16183]

Except Netflix. They prefer their annoying as hell carousels. 

 

I was talking about our apps on those platforms...

[joshua4 12]

I was talking about our apps on those platforms...

 

Oh. Then WTF LUKE

[ebr 16183]

It isn't as easy to do with html and we are working as hard and as fast as we can .

[joshua4 12]

It isn't as easy to do with html and we are working as hard and as fast as we can .

 

3 years 

[atomicmoon 152]

Chiming in, I too would like less pages, but if anything, how about placing a "next/previous" page button at the bottom? It's at the top so when you get to the bottom and realize you need to go to the next page, you have to scroll all the way back to the top just to click next page. For me, this would be a small step in a faster browsing experience from the web ui at least.