Hybrid View
-
21 Apr 2012 11:03 PM #1
TextArea loses cursor on FormPanel scrolling
TextArea loses cursor on FormPanel scrolling
Sencha Touch version tested:
- 1.1
- iOS 5
- Google Chrome
- Scrolling on a FormPanel causes textarea fields to lose their cursor. The textarea field does not adjust its cursor offset and thus it looks like you're typing but the textarea isn't scrolling after the cursor.
See this URL : http:// Steps to reproduce the problem:Code:new Ext.Application({ launch : function() { new Ext.form.FormPanel({ fullscreen : true, scroll : 'vertical', items : [ { xtype : 'textareafield', label : 'hello' }, { xtype : 'textareafield', label : 'hello2' }, { xtype : 'textareafield', label : 'hello3' } ] }) } })- Scroll down the scroller
- Begin typing into text area field and use newlines.
- Textarea would follow cursor.
- After your text begins to pass visible area, the textarea does not follow properly. The lower in the page the textarea is, the greater the gap between the cursor position and the internal textarea scroller offset.
- none
- not provided
-
23 Apr 2012 8:59 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,641
- Vote Rating
- 434
I can reproduce this using Chrome but not iOS 5 (iOS Simulator and iPhone 4S). What did you test on?
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.
-
23 Apr 2012 4:12 PM #3
Here it is using the iOS simulator
You found a bug! We've classified it as
TOUCH-2821
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote