UITableView behaviour is not what Apple engineer told me
| Originator: | pitiphong.ph | ||
| Number: | rdar://27388852 | Date Originated: | 16/07/2016 |
| Status: | Open | Resolved: | No |
| Product: | iOS SDK | Product Version: | 9.3 |
| Classification: | Bug | Reproducible: | Always |
and I can file a radar if it’s not so here the radar rdar://Summary: I have a containment controller which its view is a big scroll view and has 2 child view controllers. The top one's view is a detail view and the bottom one's view is a table view. I want these 2 child view controllers scrolled like it's the same view. I asked an Apple engineer during WWDC about is there a better way than this way because I worry about the table view performance (cell for row to be precise). But Apple engineer told me that I don't have to worry about that because table view implementation take the visible bounds on the window to do cell for row not its bound and he told me that this is an expected behaviour of table view, if I found that table view does not work this way, I can file a radar. But I found that it's not like what he told me. Table view uses its bound to do cell for row not the visible frame on window. So here's the radar for that :) Steps to Reproduce: 1. Open the sample project, build and run 2. Scroll the view. OR 1. Create a table view and set its bound to cover all of its cells 2. Add it to the scroll view Expected Results: Cell for row get called when scrolling Actual Results: Cell for row get called for every cell during view did load. Version: iOS 9.3 Notes: Configuration: iOS Simulator Attachments: 'TableView.zip' was successfully uploaded.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!