[TIMOB-3219] iOS: Pull to Refresh with Section Header
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2013-05-07T09:07:19.000+0000 |
Affected Version/s | Release 3.0.0 |
Fix Version/s | 2013 Sprint 10 |
Components | iOS |
Labels | api |
Reporter | Alan Leard |
Assignee | Shameer Jan |
Created | 2011-04-15T03:39:46.000+0000 |
Updated | 2017-03-31T20:16:24.000+0000 |
Description
Pull to refresh does allows for table scrolling behind section
header.
Video to Demonstrate: http://screencast.com/t/kKYAIQiA498">http://screencast.com/t/kKYAIQiA498
Ticket Reference: http://developer.appcelerator.com/helpdesk/view/72771">http://developer.appcelerator.com/helpdesk/view/72771
Attached code for testing.
A workaround is listed in the ticket.
Attachments
File | Date | Size |
---|---|---|
app.js | 2011-04-15T03:39:46.000+0000 | 988 |
pullrefresh.js | 2011-04-15T03:39:46.000+0000 | 3285 |
Couls someone please pass me the workaround? Would be greatly appriciated..
Could someone please pass me the workaround? Would be greatly appriciated..
I'm unable to reproduce the behavior in the video demo on TiSDK 2.2.0v20120830102513. The app updates too quickly and I'm unable to test. Someone who's having the same issue, please provide an updated sample code, otherwise ticket will be marked as invalid.
If you set a timeout(say 4 seconds) on the release of the pull2refresh you will see that when scrolling the first sectionheader behaves weird while timeout.
@Arad - Did you try this test case with a more recent release?
Yes I did, currently running 2.2 still no luck. Only the first sectionheader floats wrong when pull2refresh is loading..
Hi guys, any news on this bug? Hope you can resolve it soon.
Issue cannot reproduces Tested with Titanium Studio, build: 3.0.1.201212181159 Titanium SDK version: 3.1.0 iOS iPhone Simulator:iOS SDK: 6.1 Software OS X 10.8.2 (12C60)
This issue is still unresolved according to me. Im having this problem with Titanium SDK 3.1.0 and iOS 6.1 The issue has the status resolved, but is it really?
Closing ticket as it was last updated in 2013. If the problem still persists, please file a new ticket.