[TIMOB-3215] Issue with ScrollView/TableView & TextField in it
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-06-11T17:08:21.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 2.1.0, Sprint 2012-12 API |
Components | iOS |
Labels | api, qe-port |
Reporter | Romain Salles |
Assignee | Sabil Rahim |
Created | 2011-04-15T03:39:41.000+0000 |
Updated | 2012-12-03T15:41:08.000+0000 |
Description
Hi,
I have an issue when I associate a tableview with a textfield.
As you can see in the file called bug_01.png, I have a view with a TableView and then a button.
In my table view, I have a TextField (the one with the value 122). When I click on it to edit it, then the keyboard appears and a gap is created between my TableView and my button (see bug_02.png). Meanwhile, the same space is removed from the top of my view (see the yellow arrays).
Any idea why?
PS: my window is constructed like this:
window
scrollView
tableView
section
row (with view)
section (with an headerView)
row
row
row (with the textField)
button
Attachments
File | Date | Size |
---|---|---|
bug_01.png | 2011-04-15T03:39:41.000+0000 | 34912 |
bug_02.png | 2011-04-15T03:39:41.000+0000 | 47928 |
I believe this is a similar bug related to textfields/softkeyboard inside the scrollView: http://developer.appcelerator.com/question/129653/the-size-of-scrollview-content-changes-after-hiding-the-soft-keyboard
Still an issue on 1.9.0.x, textArea are behaving normally though.
Is there any progress in this issue?
I'm seeing this same issue. I'd love to see a fix.
Any updates to this? Still an issue on 2.0.1.x - view is expanding in size greatly.
After 6 months still no updates? This issue should get more attention... It really messes with user experience.
Some test code
Verified on: SDK:2.2.0.v20120827143312 Studio:2.1.2.201208201549 Devices: iOS simulator, iPhone 3GS
According to the Fix Version of this issue it should work in the latest RC of SDK 2.1.3 yet it does not for me. The comment of [~amittal] the solution was verified on SDK 2.2.0. Is the verification version correct or the one displayed in the Fix Version of this issue?