title: UITableViewCell with autolayout left margin different on iPhone and iPad
body: <p>I am using a grouped <code>UITableView</code> with static cells for an options screen/scene. Everything is done in Xcode 6.1 / iOS 8.1.x / Storyboard using Autolayout. Within the table groups there are mixed types of cells and there are two types that cause me problems:</p>
  
  <ol>
  <li>Cells with custom style and</li>
  <li>Cells with style "Right Detail"</li>
  </ol>
  
  <p>On cell #1 I can set a constraint for the left margin between the label and the leading container. On cell #2 I cannot set any constraints in Interface Builder as far as I know. I have set the left margin on the label in cell #1 so it aligns with the label in cell #2. Everything looks fine on an iPhone, but if I show the same table on an iPad where the size of the table view's container is half the screen size, cell #2 gets more margin (dynamically?) while cell #1 maintains the absolute margin I set in the constraints. I also tried to change the left margin in cell #1 with the attribute "relative to margin" but to no avail.</p>
  
  <p>iPhone: </p>
  
  <p><img src="https://i.stack.imgur.com/FygPX.png" alt="Table on iPhone"></p>
  
  <p>iPad (with tableview width = 1/2 screen size)</p>
  
  <p><img src="https://i.stack.imgur.com/u8Q5x.png" alt="Table on iPad"></p>
  
  <p>So the question is: How do I set the constraints for the label in cell #1 so that it aligns like cell #2.</p>
  
  <p>Here is also a link to a Xcode 6.1 sample project demonstrating the problem. Run on iPhone and iPad to see the difference:</p>
  
  <p><a href="https://dl.dropboxusercontent.com/u/5252156/Code/tableViewTest.zip" rel="noreferrer">https://dl.dropboxusercontent.com/u/5252156/Code/tableViewTest.zip</a></p>
  
  <p>This question might be related to <a href="https://stackoverflow.com/questions/16619435/layout-static-table-cell-for-iphone-and-ipad">Layout static table cell for iPhone and iPad</a>, but it might also differ for iOS 8 since everything is supposed to be adaptive now. That's why I decided to post this question anyway.</p>