- If you pulled down, let the refresh complete, then let go and regrabbed the scroll view, RefreshableScrollView would still try to restore the scroll position and you'd see the scroll view jump a bit as the content inset shifted. Get rid of that by looking at `this.state.tracking` when deciding whether to restore the scroll position (need to wait for the `onResponderGrant` callback though, so used rAF for now... should switch to a latch).
- Avoid calling `setState` when the scroll position is positive since the user isn't pulling. Save some power and CPU :)
Rewrote the part for restoring the scroll position after refreshing is completed. This mimics the Twitter app in this way where the scroll view is non-interactive while it slides back up from its resting position w/the refresh indicator to its resting position without it. This is feeling close to production quality.
You could get into an aggressive flurry of refreshes if you pulled down to refresh, then kept your finger down while the refresh completes, and then moved your finger a bit to trigger another refresh.
Fix this by requiring the user to have lifted their finger (i.e. for the gesture responder to have stopped tracking) after the refresh completes before allowing a second one.