[TIMOB-27819] iOS: Incorrect listSection headerTitle spacing in iOS 13+

GitHub Issue	n/a
Type	Bug
Priority	None
Status	Open
Resolution	Unresolved
Affected Version/s	Release 8.3.0, Release 8.3.1, Release 9.3.0, Release 9.2.2
Fix Version/s	n/a
Components	iOS
Labels	ios-13, listsection, listview
Reporter	Sohail Saddique
Assignee	Vijay Singh
Created	2020-03-24T17:18:20.000+0000
Updated	2020-12-03T18:42:57.000+0000

Description

In iOS 13, in a listview, when you use:

style: Ti.UI.iOS.ListViewStyle.GROUPED

and then use the _headerTitle_ property on a _ListSection_, the spacing between the top of the window and the _ListSection_ is too close. I believe the spacing is incorrectly set on iOS 13. The spacing is set correctly on < iOS 13. Please see screenshot attached. *Steps*

Create new classic app

Replace app.js with code below. Test with iOS 12 and then iOS 13.

var win2 = Titanium.UI.createWindow({
    backgroundColor: 'lightgray',
    title: 'List Section Test'
});

var win1 = Titanium.UI.createNavigationWindow({
   window: win2
});

var listView = Ti.UI.createListView({
    style: Ti.UI.iOS.ListViewStyle.GROUPED
});
var sections = [];

var fruitSection = Ti.UI.createListSection({ headerTitle: 'Fruits'});
var fruitDataSet = [
    {properties: { title: 'Apple'}},
    {properties: { title: 'Banana'}},
];
fruitSection.setItems(fruitDataSet);
sections.push(fruitSection);

var vegSection = Ti.UI.createListSection({ headerTitle: 'Vegetables'});
var vegDataSet = [
    {properties: { title: 'Carrots'}},
    {properties: { title: 'Potatoes'}},
];
vegSection.setItems(vegDataSet);
sections.push(vegSection);

listView.sections = sections;
win2.add(listView);
win1.open();

var fishSection = Ti.UI.createListSection({ headerTitle: 'Fish'});
var fishDataSet = [
    {properties: { title: 'Cod'}},
    {properties: { title: 'Haddock'}},
];
fishSection.setItems(fishDataSet);
listView.appendSection(fishSection);

Attachments

File	Date	Size
Screen Shot 2020-03-24 at 5.14.26 PM.png	2020-03-24T17:18:04.000+0000	392541

Comments

Hans Knöchel 2020-03-26

+1, this is a valid issue.

JSON Source