ionic-framework: iOS; scrolling broken in lists with inputs
Short description of the problem:
On iOS scrolling sometimes stops working in lists. It only happens when the list consists of inputs elements like input. When input focus is obtained scrolling sometimes ceases to function. It seems to be a result of the keyboard. It is not possible to regain the ability to scroll; only by leaving the view and entering it again.
After the last two inputs I am not able to scroll. The scroll ceases to function.
What behavior are you expecting?
Scrolling should work regardless of what elements are used. Input included <ion-input>. Also with cordova.plugins.Keyboard.disableScroll(true) set scroll should reengage when keyboard disappears.
Steps to reproduce:
- set
cordova.plugins.Keyboard.disableScroll(true) - Make a view with a
<div class="list> - Fill the div with inputs
<ion-input> - Scroll down to the bottom elements
- Select element for input
- Close the keyboard
- Scrolling is now ‘locked’ and not possible (this is not completely reproducible, but it happens very frequently)
Ionic Version: 1.2.x
Browser & Operating System: iOS 9.3 or lower
Run ionic info from terminal/cmd prompt:
Cordova CLI: 5.1.1
Gulp version: CLI version 3.9.0
Gulp local: Local version 3.9.0
Ionic Version: 1.2.4-nightly-1917
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
ios-deploy version: 1.7.0
ios-sim version: 4.1.1
OS: Mac OS X El Capitan
Node Version: v0.12.2
Xcode version: Xcode 7.2.1 Build version 7C1002
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 5
- Comments: 17 (5 by maintainers)
Yes your code works.
I’ve discovered the root to the problem. Native scrolling. I thought I had only disabled javascript scrolling for Android but in fact I disabled it on all platforms.
So the root of this problem was;
$ionicConfigProvider.scrolling.jsScrolling(false). This breaks scrolling on iOS in some cases. I’m sorry but it is something I only just realized.I guess you can close this issue now. Again sorry for the trouble.
This is a pretty significant problem!
Anyone have a fix until this is properly taken care of?