-
Notifications
You must be signed in to change notification settings - Fork 85
ion-refresher always fired when pulling up at any position in the page (middle,bottom) not only on top of the page. #386
Comments
I'm experiencing the same problem on ionic 4 |
Same problem here. |
Same issue, all pull down fired even in the middle. Ionic: Ionic CLI : 5.4.1 (C:\Users****\AppData\Roaming\npm\node_modules\ionic) Cordova: Cordova CLI : not installed Utility: cordova-res : 0.8.1 System: Android SDK Tools : 26.1.1 (C:\Android\sdk) |
is there any update for this? |
Hi, I think this error sometimes occurs because the refresh event is not over by using;
and then every clicks trigger the event again. You can give time out to your event.
Use it in doRefresh event handler just like this;
So if the event is not over by using;
Timeout will end it. |
Original issue by @jayzyaj on 2018-07-18T06:32:55Z
Bug Report
I need to make 3 slides using ion-slides component after adding ion-refresher component to my page the ion-refresher always fired when pulling up at any position in the page (middle,bottom) not only on top of the page.
Ionic Info
Describe the Bug
ion-refresher pull icon always shows up even at the bottom center page which will only be showed when on the most top part of the page. I am using ion-slides and any slide has an issue when scrolling up. It already shows the refresher even when I am not on the top of the page
Steps to Reproduce
Steps to reproduce the behavior:
Related Code
stackoverflow
stackoverflow2
`
<ion-slides #mySlider (ionSlideDidChange)="onSlideChanged($event)" *ngIf="!spinner">
`
Expected Behavior
Pulling icon of the refresher is supposed to show at the most top part of the slide or page. But always shows when scrolling up at the bottom part of the slide or content even at the middle
Additional Context
List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, screenshots, OS if applicable, etc.
The text was updated successfully, but these errors were encountered: