New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TIMOB-9944] Do not override UIResponder chain for touchDelegate #2698
Conversation
- (void) reloadAndRestoreSelection | ||
{ | ||
NSIndexPath* curSelected = [[self tableView] indexPathForSelectedRow]; | ||
[[self tableView] reloadData]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, this scares me. ReloadData is VERY expensive and worse yet, has in the past stomped on interface state machines and caused tables to become unresponsive. Are you sure reloadData is needed?
TableView will internally only redisplay rows that are visible so it should not be very expensive, however I see an issue here when table is editing or moving at which point it would cause problems. Hold off on FR |
Ready for review |
CR passed, but will be checking to see why we had that touchDelegate in the first place. |
FR passed. merging. |
[TIMOB-9944] Do not override UIResponder chain for touchDelegate
Test is in JIRA
See the video mentioned in the comments to reproduce the issue.