Home/subscription scrolling state lost on navigation #1402

Closed
opened 2018-04-26 23:13:29 +02:00 by tzarebczan · 2 comments
tzarebczan commented 2018-04-26 23:13:29 +02:00 (Migrated from github.com)

The Issue

If you navigate horizontally using the arrows on the home/subscription pages, go into a claim, then go back, you end up at the left-most position (resets). Shouldn't it go back to where it was previously scrolled to?

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 live chat at https://chat.lbry.io --> ## The Issue If you navigate horizontally using the arrows on the home/subscription pages, go into a claim, then go back, you end up at the left-most position (resets). Shouldn't it go back to where it was previously scrolled to? ## 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' --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 -->
neb-b commented 2018-04-28 01:24:56 +02:00 (Migrated from github.com)

I would say ideally it would, but it would be a decent amount of work. It
would require moving this data outside of the component, and into the redux
store. It wouldn't be that hard, but time consuming.

This would probably live in the app reducer

On Thu, Apr 26, 2018 at 5:13 PM, Thomas Zarebczan notifications@github.com
wrote:

The Issue

If you navigate horizontally using the arrows on the home/subscription
pages, go into a claim, then go back, you end up at the left-most position
(resets). Shouldn't it go back to where it was previously scrolled to?
System Configuration

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

Anything Else Screenshots


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/1402, or mute the thread
https://github.com/notifications/unsubscribe-auth/AQGcjuqgN9KlljTIbr5EhAv1YOPqrcMwks5tsjh7gaJpZM4Tn4Rb
.

I would say ideally it would, but it would be a decent amount of work. It would require moving this data outside of the component, and into the redux store. It wouldn't be that hard, but time consuming. This would probably live in the `app` reducer On Thu, Apr 26, 2018 at 5:13 PM, Thomas Zarebczan <notifications@github.com> wrote: > The Issue > > If you navigate horizontally using the arrows on the home/subscription > pages, go into a claim, then go back, you end up at the left-most position > (resets). Shouldn't it go back to where it was previously scrolled to? > System Configuration > > - LBRY Daemon version: > - LBRY App version: > - LBRY Installation ID: > - Operating system: > > Anything Else Screenshots > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/1402>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AQGcjuqgN9KlljTIbr5EhAv1YOPqrcMwks5tsjh7gaJpZM4Tn4Rb> > . >
tzarebczan commented 2019-07-24 03:52:22 +02:00 (Migrated from github.com)

This is no longer valid for the new app. Please open any restoration issue separately.

This is no longer valid for the new app. Please open any restoration issue separately.
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#1402
No description provided.