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

[Android][SectionList/FlatList] scrollTo not working because offset is outside rendered "canvas" #15695

Closed
peterjuras opened this issue Aug 29, 2017 · 1 comment
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@peterjuras
Copy link
Contributor

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

  1. react-native -v: 0.46.4
  2. node -v: 8.1.4
  3. npm -v: 5.3.0
  4. yarn --version: 0.27.5

Then, specify:

  • Target Platform: Android
  • Development Operating System: macOS
  • Build tools: irrelevant for bug

Steps to Reproduce

In general, I am trying to preserve scroll position when a user navigates away from a ListView and then back again.

  1. Display a or (I'm using SectionList for my use case) with 1000 items à ~50 pixels height
  2. In componentDidMount scroll to an offset that is deep down the list (e.g. offset 1000). You can use the scrollTo method of the underlying ref (this.sectionList._wrapperListRef._listRef) or implement getItemLayout and use scrollToLocation*
  3. Wrap the scrollTo* call in a setTimeout(... scrollTo ..., 0)

Expected Behavior

On Android it should scroll until the desired position, just like on iOS.

Actual Behavior

-> On iOS it is working, on Android it will only scroll until the 10th item, because only 10 items are rendered initally

Workaround: Setting initialNumToRender to 1000 will work, but this might crash on low end devices.

Reproducible Demo

Please check out this CRNA sample to reproduce the bug:
https://github.com/peterjuras/rn-list-scrollTo-bug

@stale
Copy link

stale bot commented Oct 28, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 28, 2017
@stale stale bot closed this as completed Nov 4, 2017
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

1 participant