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

[SectionList] Cannot scroll to top of a SectionList with Header #14392

Closed
mikelambert opened this issue Jun 8, 2017 · 3 comments
Closed

[SectionList] Cannot scroll to top of a SectionList with Header #14392

mikelambert opened this issue Jun 8, 2017 · 3 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@mikelambert
Copy link
Contributor

mikelambert commented Jun 8, 2017

SectionList.scrollToLocation internally calls VirtualizedList.scrollToIndex. Calling it with {itemIndex: 0, sectionIndex: 0} will scroll to the first element, but in the case of a header, will leave the header offscreen.

In writing this up, I discovered an ugly hack workaround that takes advantage of the calculation code: {itemIndex: 0, sectionIndex: 0, viewPosition: 100} will scroll to the top of the page (or some sufficiently high number to guarantee the code clamps to 0).

@jstheoriginal
Copy link
Contributor

jstheoriginal commented Jul 18, 2017

I believe viewOffset param is what you should use, with it equal to the height of the header, as this is what the documentation notes.

@kelset
Copy link
Contributor

kelset commented Jul 25, 2017

viewOffset worked fine for me, in version 0.46.4.

( I think this issue can be closed tbh)

@pull-bot
Copy link

pull-bot commented Oct 9, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Oct 9, 2017
@hramos hramos closed this as completed Oct 9, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Oct 9, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Oct 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants