[TIMOB-3354] TextView within TableViewRow scrolling/jumping when focussed
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2011-04-15T03:43:08.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.7.0, Sprint 2011-11 |
Components | iOS |
Labels | ios, iphone, jumping, mobile, modal, release-1.7.0, scrolling, tableview, tableviewrow, textview, window |
Reporter | Cedric Kastner |
Assignee | Reggie Seagraves |
Created | 2011-04-15T03:43:07.000+0000 |
Updated | 2017-03-03T06:18:27.000+0000 |
Description
Titanium Version 1.2.2 with Mobile 1.6.0 for iOS
Description: If you create a modal window with TableView that contains TableViewRows with TextField controls, the TableView is scrolling/jumping to a wrong position when focussed.
Additional note: Scrolling/jumping does not occure when the height of all TableViewRows is greater than the available screen height. You can use a pseudo-workaround by setting the height of TableView to the exact height of all TableViewRows, but this helps in Simulator (no Retina) only.
How to reproduce: Create an empty Titanium project and replace the content of app.js with the source in this https://gist.github.com/854344">GIST, then run iOS-Simulator for testing.
New temporary workaround You can fill up the
empty space at the bottom of the TableView by setting the
"footerTitle" property to linebreaks only. Example:
Ti.UI.createTableView({footerTitle: '\n\n\n\n\n'});
Note: You may need to add additional linebreaks depending on how many rows the TableView has…
This is related to or a duplicate of ticket 2907. Assigning to Blain and scheduling for the current sprint.
(from [f51f1e1a643cfe556882785e9a683698ad704070]) [#3354 state:fixed-in-qa] [#2907 state:fixed-in-qa] It feels good to find a one-liner fix after doing all these deep changes (offset should never be negative) https://github.com/appcelerator/titanium_mobile/commit/f51f1e1a643cfe556882785e9a683698ad704070"> https://github.com/appcelerator/titanium_mobile/commit/f51f1e1a643c...
Actually, let's do one better. This is a dupe of #2907
Closing issue due to time passed and irrelevance of the ticket.