UX Enhancement: Way to cycle through a user's claims #453

Open
opened 2017-08-08 05:28:07 +02:00 by chickenpie347 · 0 comments
chickenpie347 commented 2017-08-08 05:28:07 +02:00 (Migrated from github.com)

The Issue

Right now if I go to any channel, I can click on some content and if I want to watch the next one, I have to go back and then click the next one. I think that's an additional step that can be eliminated.

Can we have something like: "<- Previous Claim By User" "Next Claim By User ->" buttons on the claim page that let you cycle through all of the given channel/user's claims?

Steps to reproduce

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

System Configuration

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

Anything Else

Screenshots

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on Slack at https://slack.lbry.io --> ## The Issue Right now if I go to any channel, I can click on some content and if I want to watch the next one, I have to go back and then click the next one. I think that's an additional step that can be eliminated. Can we have something like: "<- Previous Claim By User" "Next Claim By User ->" buttons on the claim page that let you cycle through all of the given channel/user's claims? ### Steps to reproduce 1. 2. 3. ### Expected behaviour Tell us what should happen ### Actual behaviour Tell us what happens instead ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279/lbryapi' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#453
No description provided.