title: iOS 8 UITableView rotation bug
body: <p>So after compiling an app on XCode 6, I noticed a strange bug that happens only when running on iOS 8:
  The <code>UITableView</code> takes the wrong <em>inner</em> dimensions after updating its frame.</p>
  
  <p>Now I'll try to explain the exact situation:
  We have a <code>UITableView</code> rotated on its side, which basically makes a horizontal <code>UITableView</code>. It happens through <code>tableView.transform = CGAffineTransformMakeRotation(-M_PI / 2);</code>.
  Now after setting the transform, and then settings its frame - everything is fine.
  But of course the system in most cases sends the parent another frame change because it needs to set the parent to the real sizes and not the XIB sizes or any initialization size. In that moment - when I relayout the subviews, including the table view - everything goes wrong.
  Actually the frame of the table view is simply set to the <code>bounds</code> of the containing view, but then the inner scrollview (In iOS 8 the <code>UITableView</code> has another <code>UIScrollView</code> inside it, called <code>UITableViewWrapperView</code>. As <code>UITableView</code> is a <code>UIScrollView</code> by itself, I can't figure out why they needed another one...) takes a "height" which equals the parent width. And "height" is actually the <code>width</code> property, only rotated.</p>
  
  <p>Now we can easily estimate the they have a bug with relating the width of the inner <code>UIScrollView</code> to the actual width of the parent <code>UITableView</code>, which could possibly be by reading the <code>.frame.size.width</code> instead of the <code>.bounds.size.width</code>. 
  But the strange thing is that when investigating the frame of the subviews of the <code>UITableView</code>- it seems that they are all good! So it must be a <em>rendering</em> problem somewhere.</p>
  
  <p>So we are left with a horizontal table which has a blank gap on top, because the "height" of the cells is 320 instead of 568, while the "width" of the cells is fine, set to 320.</p>
  
  <p>I'll be very happy to hear from other people experiencing this problem (Or from Apple), but I have finally found a solution and posting it here with the question, for future reference for me and for others.</p>