[TIMOB-1477] Standalone window with grouped view does not display section rows
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2012-06-25T12:04:31.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | defect, ios, iphone |
| Reporter | Kevin Whinnery |
| Assignee | Neeraj Gupta |
| Created | 2011-04-15T02:53:54.000+0000 |
| Updated | 2017-03-09T22:46:26.000+0000 |
Description
Community member reported the following issue with table views which I have confirmed on a 1.4.0 and 1.4.1 pre-release build. Here's the Q&A issue:
http://developer.appcelerator.com/question/48511/tableview-without-a-tabgroup--no-rows-bug"> http://developer.appcelerator.com/question/48511/tableview-without-...
To see it in action, try to open this window standalone in app.js (i.e. not in a tab group), and you will notice that the rows added to the table view section do not display. If you add the same window to a tab group, the rows are displayed fine.
app.js:
http://pastie.org/1068568">http://pastie.org/1068568
newWindow.js:
http://pastie.org/1068569">http://pastie.org/1068569
Hi,
Is there any update on this issue? I can't seem to find a workaround to get custom layouts happening in a table view that doesn't belong to a window inside a tab group. This seems like a pretty important bug no?
I also notice this problem (with table views and tab groups) manifests itself in the KitchenSink. You might have to try a few times - go to Phone, Camera, one of the camera examples and then back to the examples list. You find in some cases the table is re-rendered without any of the tab groups. At this point the table no longer accepts events and the app effectively is dead. There is no way to navigate. The only way to recover is to kill the app via the iOS 4's background tasks.
Is there a workaround?
thanks,
dave
Is this not being fixed for 1.5? It's a huge bug, reported 4 months ago, and confirmed by an Appcelerator dev. I'm using a continuous build from yesterday and it's still broken.
I can't even begin to describe the amount of suffering this bug has caused and is still causing me to this day. I can't believe it's not being addressed for 1.5.
rollback wrong update
This issue has probably been fixed as a part of some other fix. We cannot reproduce it with the 2.1.0 release.
Closing ticket as the issue cannot be reproduced.