title: iOS6 and offscreen UITextView in UITableView
body: <p>I have a UITableViewController that has a UITextField in each cell. When the user hits return in a field, it automatically sets the next field to be first responder and scrolls the table to show that field, like this:</p>
  
  <pre><code>- (BOOL) textFieldShouldReturn:(UITextField *)textField 
  {  
      UITextField *nextTextField=nil;
      NSInteger row;
      NSInteger section;
  
      if(textField == self.txtFieldA) 
      {
          nextTextField = self.txtFieldB;
          row=1; section=0;
      }
      else if(textField == self.txtFieldB) 
      {
          nextTextField = self.txtFieldC;
          row=2; section=0;
      }
      else 
      {
          [textField resignFirstResponder];
      }
  
      if(nextTextField) 
      {        
          NSIndexPath *indexPath = [NSIndexPath indexPathForRow:row inSection:section];
          [nextTextField becomeFirstResponder];
  
          [self.tableView scrollToRowAtIndexPath:indexPath atScrollPosition:UITableViewScrollPositionBottom animated:YES];      
      }
  }
  </code></pre>
  
  <p>The issue comes when you select a text field (say txtFieldA), scroll the table down so that txtFieldB is not visible, then hit enter. It works as expected on iOS5 (txtFieldB becomes the new first responder). However, on iOS6 it doesn't. It scrolls to the correct spot in the table, but the txtFieldB does not become the first responder (and I'm not sure what is -- when I hit "Back" on my nav controller, the keyboard stays visible).</p>
  
  <p>When I hit "Return", txtFieldB's didBeginEditing isn't fired. If I delay <code>[nextTextField becomeFirstResponder]</code> by a second or so (until the scrolling animation finishes which makes nextTextField visible) it works as expected, but it seems hacky and less smooth to do that so I would rather understand what's going wrong than implement something like that.</p>