[Scroll] RFC: Add scrollWithoutAnimationTo to immediately scroll #486
+22
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is an API like setting the contentOffset except it is imperative, which is usually what you want unless the scroll view is a controlled component.
Contributor
Totally agreed. This looks good to me |
Contributor
Author
|
closing in favor of #509 w/suggested changes |
vjeux
pushed a commit
to vjeux/react-native
that referenced
this pull request
Apr 13, 2015
Summary: Implementing the consensus approach from the comments on this PR: facebook#486 We use a boolean flag in the Obj-C code to determine whether to animate or not, and then provide two public JS functions that call the Obj-C with or without the flag. Closes facebook#509 Github Author: Charlie Cheever <[email protected]> Test Plan: Imported from GitHub, without a `Test Plan:` line.
vjeux
pushed a commit
to vjeux/react-native
that referenced
this pull request
Apr 14, 2015
Summary: Implementing the consensus approach from the comments on this PR: facebook#486 We use a boolean flag in the Obj-C code to determine whether to animate or not, and then provide two public JS functions that call the Obj-C with or without the flag. Closes facebook#509 Github Author: Charlie Cheever <[email protected]> Test Plan: Imported from GitHub, without a `Test Plan:` line.
vjeux
pushed a commit
to vjeux/react-native
that referenced
this pull request
Apr 15, 2015
Summary: Implementing the consensus approach from the comments on this PR: facebook#486 We use a boolean flag in the Obj-C code to determine whether to animate or not, and then provide two public JS functions that call the Obj-C with or without the flag. Closes facebook#509 Github Author: Charlie Cheever <[email protected]> Test Plan: Imported from GitHub, without a `Test Plan:` line.
This was referenced Jan 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an API like setting the contentOffset except it is imperative, which is usually what you want unless the scroll view is a controlled component (for that to be realistic, JS would need to drive the scroll physics and specify the contentOffset during each frame without interruptions like the GC or CPU-hungry JS).