-
26 Jul 2012 3:01 PM #1
Scrolling Glitch After Using the iOS Soft Keyboard in a Form Panel
Scrolling Glitch After Using the iOS Soft Keyboard in a Form Panel
REQUIRED INFORMATION
Sencha Touch versions tested:- 2.0.1
- 2.0.1.1
- Safari (on iOS 5.1.1)
- Chrome 19.0.1084.60 (on iOS 5.1.1)
- html (as in HTML5)
- When you use the 'Next' button in the iOS soft keyboard when on a Form Panel and it has to 'scroll' to the next text field, it creates a glitch in the scrolling after you've closed the keyboard with 'Done'.
- Tap the first text field
- Tap 'Next' a few times on the soft keyboard that appears to get to the last text field
- Tap 'Done'
- Begin to scroll
- The page should scroll from where the soft keyboard left it
- The view instantly jumps to the top of the panel and starts scrolling from there
HELPFUL INFORMATIONCode:Ext.Loader.setConfig({ enabled: true }); Ext.application({ name: 'SenchaFiddle', launch: function() { Ext.Viewport.add(Ext.create('Ext.form.Panel', { items: [{ xtype: 'textfield', placeHolder: 'text', minHeight: '400px' }, { xtype: 'textfield', placeHolder: 'text', minHeight: '400px' }, { xtype: 'textfield', placeHolder: 'text', minHeight: '400px' }] })); } });
Additional CSS used:- only default sencha-touch.css
- iOS 5.1.1
-
27 Jul 2012 7:38 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
Thanks for the report.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
2 Aug 2012 6:46 PM #3
You found a bug! We've classified it as
TOUCH-3178
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote