Note that there are some explanatory texts on larger screens.

plurals
  1. POGrouped UITableView has 20px of extra padding at the bottom
    text
    copied!<p>Grouped table views seem to have extra padding on the bottom in iOS 6 (iOS 5 does not have it), but I can't find any documentation that suggests this is correct / expected behavior.</p> <p>This affects the example projects as well, for instance the <code>SimpleTableView</code> project in the <code>TableViewSuite</code> example. I think I had to change the style in the <code>AppDelegate</code> to 'grouped', and updated the SDK to iOS 6, but no other changes have been made to the project.</p> <p>Investigating revealed that there are <code>10px</code> reserved for header and footer views, plus some <code>20px</code> that can't be accounted for. There are no actual header or footer views (<code>tableHeaderView</code> and <code>tableFooterView</code> are <code>nil</code>, and implementing and returning <code>nil</code> for e.g. <code>viewForFooterInSection</code> does nothing). I cannot find any '20' value on the tableView itself, though I may have missed something of course.</p> <p>Adding a zero-size view for the footer does nothing, but adding a <code>1px</code> square view causes the extra padding to vanish. e.g.:</p> <pre><code>tableView.tableFooterView = [[UIView alloc] initWithFrame:CGRectMake(0,0,1,1)]; </code></pre> <p>It does take up <code>1px</code> of height still, so the bottom padding is now <code>11px</code>, but this is far less noticeable than 20. And now setting the <code>sectionFooterHeight</code> to 0 will result in only <code>1px</code> of bottom-space.</p> <p>My question is: what? And how can I completely remove it? This isn't anything mission-critical, but it is extremely weird, undesirable, and as far as I can tell it's undocumented. </p> <p>Please note - its copy past question from apple dev forum. But I have exactly the same issue and I don't understand how to solve it too.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload