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

Broaden [RefreshControl][ScrollView] behaviour, customise refresh indicator - PullableView? #20396

Closed
peetzweg opened this issue Jul 25, 2018 · 3 comments
Labels
Stale There has been a lack of activity on this issue and it may be closed soon. Type: Discussion Long running discussion.

Comments

@peetzweg
Copy link

peetzweg commented Jul 25, 2018

For Discussion

I was looking for a way to fire an action if the user pulled the top of the list. Usually this leads in most apps to an refresh of the list and this is what was implemented with the RefreshControl Component in the ScrollView and its components alike.
However, some apps on iOS at least have implemented a way to pull the current view down and focusing on a new component which is thereby pulled into view.
I hope this is understandable. This might not be elegant to implement in the ScrollView or with an extened RefreshControl because this 'PullableView' should not be scrollable. Anyway I think this behaviour is somehow related to the RefreshControl and thereby ended up here.

@react-native-bot react-native-bot added the Type: Discussion Long running discussion. label Jul 25, 2018
@peetzweg
Copy link
Author

Examples

  1. In Bear I can pull down a search input from the top.
    pulldown

  2. In Poncho the Refresh Indicator which is pulled from the top is customized to be Poncho's hand with a figdget spinner, which is btw genius. 👏
    poncho

@peetzweg peetzweg changed the title Broaden [RefreshControl][ScrollView] behaviour - pull down Broaden [RefreshControl][ScrollView] behaviour, customise refresh indicator - PullableView? Jul 26, 2018
@stale
Copy link

stale bot commented Feb 2, 2019

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. 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 Feb 2, 2019
@stale
Copy link

stale bot commented Feb 9, 2019

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Feb 9, 2019
@facebook facebook locked as resolved and limited conversation to collaborators Feb 10, 2019
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. Type: Discussion Long running discussion.
Projects
None yet
Development

No branches or pull requests

2 participants