MobileRead Forums - View Single Post - Can only browser content server from beginning

philipsd6 · 12-28-2017, 10:26 AM

I'm really enjoying the new content server, but several things that are really bothering me are:

If I've clicked "Show more books" multiple times to go further back in my library, and then sometime later I want to start browsing back from that point -- I cannot. I have to start all over again. There's no concept of "pagination" here. And since sometimes the browse list resets back to the beginning if the page has to refresh for any reason, that makes it very difficult and frustrating to get back to the point I left off at.

I also cannot right-click on a book and open the details in a new tab, which would be very handy, and would leave the browse list untouched while I check out the book details, or open it for reading.

Is anyone else having these problems? I'd really like to have the web UI follow browser standards -- sort keys, order, and pagination in the URL instead of hidden away in Javascript. Book covers that are actual normal hrefs instead of onClick handlers so we can do normal things with web links. WDYT?

12-28-2017, 10:26 AM	#1
philipsd6 Above Average Member Posts: 1 Karma: 10 Join Date: Dec 2017 Device: iPhone 7 w/ Marvin 3	Can only browser content server from beginning I'm really enjoying the new content server, but several things that are really bothering me are: If I've clicked "Show more books" multiple times to go further back in my library, and then sometime later I want to start browsing back from that point -- I cannot. I have to start all over again. There's no concept of "pagination" here. And since sometimes the browse list resets back to the beginning if the page has to refresh for any reason, that makes it very difficult and frustrating to get back to the point I left off at. I also cannot right-click on a book and open the details in a new tab, which would be very handy, and would leave the browse list untouched while I check out the book details, or open it for reading. Is anyone else having these problems? I'd really like to have the web UI follow browser standards -- sort keys, order, and pagination in the URL instead of hidden away in Javascript. Book covers that are actual normal hrefs instead of onClick handlers so we can do normal things with web links. WDYT?