Clean up weird comment in ReactScrollView (#54807)

Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54807

Was reading this code and this comment seems unnecessary. Was added in 2016 0_0

Changelog: [Internal]

Reviewed By: fabriziocucci

Differential Revision: D88509989

fbshipit-source-id: 2179f7a34805858b34024b7a3ff65fd0287f9ced
This commit is contained in:
Joe Vilches authored and meta-codesync[bot] committed 2025-12-05 18:11:47 -08:00
1 parent a9a0268953
commit 63b0aef13e
1 file changed
+1 -10
@@ -780,8 +780,6 @@ public class ReactScrollView extends ScrollView
if (mPagingEnabled) {
flingAndSnap(correctedVelocityY);
} else if (mScroller != null) {
// FB SCROLLVIEW CHANGE
// We provide our own version of fling that uses a different call to the standard OverScroller
// which takes into account the possibility of adding new content while the ScrollView is
// animating. Because we give essentially no max Y for the fling, the fling will continue as
@@ -806,8 +804,6 @@ public class ReactScrollView extends ScrollView
);
ViewCompat.postInvalidateOnAnimation(this);
// END FB SCROLLVIEW CHANGE
} else {
super.fling(correctedVelocityY);
}
@@ -1266,11 +1262,8 @@ public class ReactScrollView extends ScrollView
@Override
protected void onOverScrolled(int scrollX, int scrollY, boolean clampedX, boolean clampedY) {
if (mScroller != null && mContentView != null) {
// FB SCROLLVIEW CHANGE
// This is part two of the reimplementation of fling to fix the bounce-back bug. See #fling()
// for
// more information.
// for more information.
if (!mScroller.isFinished() && mScroller.getCurrY() != mScroller.getFinalY()) {
int scrollRange = getMaxScrollY();
@@ -1279,8 +1272,6 @@ public class ReactScrollView extends ScrollView
scrollY = scrollRange;
}
}
// END FB SCROLLVIEW CHANGE
}
if (ReactNativeFeatureFlags.shouldTriggerResponderTransferOnScrollAndroid()