[TIMOB-15891] iOS: TableView doesn't keep its contentInsets

GitHub Issue	n/a
Type	Bug
Priority	Medium
Status	Open
Resolution	Unresolved
Affected Version/s	n/a
Fix Version/s	n/a
Components	n/a
Labels	inset, tableview, textfield
Reporter	Matej
Assignee	Unknown
Created	2013-12-04T11:25:12.000+0000
Updated	2018-02-28T20:03:20.000+0000

Description

- TableView has no inset so in the application that I provided below you can't see any red space on the top of the TableView or in the bottom. (You can also try to set smaller inset it is not working as well) - If you tap on some TextField (Focus it), TableView will have default inset (This is not really problem), but if you close the keyboard inset is still there... (You can see big red space on the top/in the bottom). *index.js*

$.win.open();

*index.tss*

"Window":{
	backgroundColor: "white"
}

"TableView":{
	width: Ti.UI.FILL, height: Ti.UI.FILL,
	backgroundColor: "red",
	style: Ti.UI.iPhone.TableViewStyle.GROUPED,
	contentInsets: {top: -35, bottom: -35}
}

"TableViewRow":{
	width: Ti.UI.FILL, height: Ti.UI.FILL
}

"TextField":{
	width: Ti.UI.FILL, height: Ti.UI.FILL,
	backgroundColor: "#CCCCCC"
}

*index.xml*

<Alloy>
    <Window id="win">
    	<View width="Ti.UI.FILL" height="250" bottom="0">
	    	<TableView>
	    		<TableViewRow>
	    			<TextField value="Value"></TextField>
	    		</TableViewRow>
	    		
	    		<TableViewRow>
	    			<TextField value="Value"></TextField>
	    		</TableViewRow>
	    		
	    		<TableViewRow>
	    			<TextField value="Value"></TextField>
	    		</TableViewRow>
	    		
	    		<TableViewRow>
	    			<TextField value="Value"></TextField>
	    		</TableViewRow>
	    		
	    		<TableViewRow>
	    			<TextField value="Value"></TextField>
	    		</TableViewRow>
	    		
	    		<TableViewRow>
	    			<TextField value="Value"></TextField>
	    		</TableViewRow>
	    	</TableView>
    	</View>
    </Window>
</Alloy>

Comments

Ingo Muschenetz 2014-03-12

We don't have enough bandwidth in 3.2.3, so saving this for 3.3.0.
Unknown 2014-04-21

This issue was previously scheduled to be worked on in more than one sprint: * 'Release 3.1.2' (on board '3.1.X Triage') * 'Release 3.0.1/TS 3.0.2' (on board '3.1.0 Triage') * 'Release 3.2.3' (on board '3.2.X Triage') Starting from JIRA Agile 6.3, an issue can only belong to a single future sprint. Read more about this change: http://docs.atlassian.com/agile/docs-0630/Sprint+Marker+Migration This issue is now scheduled for future sprint 'Release 3.1.2' (on board '3.1.X Triage'). If this is incorrect, please update the issue accordingly. This comment was automatically generated by JIRA. If it is no longer relevant, please feel free to delete it.

JSON Source