Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "go to page" navigation to channel pagination options #711

Closed
tzarebczan opened this issue Nov 2, 2017 · 0 comments · Fixed by #1166
Closed

Add "go to page" navigation to channel pagination options #711

tzarebczan opened this issue Nov 2, 2017 · 0 comments · Fixed by #1166
Labels
good first issue help wanted level: 1 No knowledge of the existing code required type: improvement Existing (or partially existing) functionality needs to be changed

Comments

@tzarebczan
Copy link
Contributor

The Issue

For channels with many pages of content, the current pagination option allows you to skip forward one or two pages or click the last 2. There is no option to go directly to a particular page. The current workaround would be to change the page number in the address bar.

Would be a good feature to add - possibly by clicking the ellipses (need to indicate this somehow) or having a separate "Go to Page" option altogether.

Steps to reproduce

  1. Go to lbry://@NileRed
  2. Can go forward a couple pages or to the end

Expected behaviour

Allow users to skip to any page they want

Actual behaviour

Can skip page by page, or use address bar

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

@tzarebczan tzarebczan added contributor friendly type: improvement Existing (or partially existing) functionality needs to be changed labels Nov 2, 2017
@liamcardenas liamcardenas added help wanted level: 1 No knowledge of the existing code required and removed contributor friendly labels Dec 15, 2017
Ruk33 pushed a commit that referenced this issue Feb 25, 2022
* Upgrade reach ui to latest to address "observe" warning

* Amend changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue help wanted level: 1 No knowledge of the existing code required type: improvement Existing (or partially existing) functionality needs to be changed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants