You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have cards in my ion-content. Say, 20. Scrolling to bottom goes smooth as it should. But, being almost at the bottom of the content and then scrolling/swiping to go up, immediately jumps to top of the content. To test the issue in browser, click and hold content and try to swipe up.
This looks like a total mess in browser and on device (android) I've tested. Unsure if this is a performance issue or just a bug, but it looks horrible.
Affected platforms (couldn't test on iOS):
Android 5.1.1
Google Canary [latest]
Google Chrome 48.0.2564.116 m
I did noticed an console.info popping up in Chrome: Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted.(pull-to-refresh.js:335)
Thank you for looking into it.
The text was updated successfully, but these errors were encountered:
@adamdbradley: Yes, I am using pull to refresh. Will create new repo and post it here in few minutes. I'd say it has alot to do with another issue I've posted: #5550
Type: bug
Ionic Version: 2.x
Platform: all
I have cards in my
ion-content
. Say, 20. Scrolling to bottom goes smooth as it should. But, being almost at the bottom of the content and then scrolling/swiping to go up, immediately jumps to top of the content. To test the issue in browser, click and hold content and try to swipe up.This looks like a total mess in browser and on device (android) I've tested. Unsure if this is a performance issue or just a bug, but it looks horrible.
Affected platforms (couldn't test on iOS):
I did noticed an console.info popping up in Chrome:
Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted.
(pull-to-refresh.js:335)Thank you for looking into it.
The text was updated successfully, but these errors were encountered: