Bug 32857 - ListView IsPullToRefreshEnabled=false during refresh breaks layout
Summary: ListView IsPullToRefreshEnabled=false during refresh breaks layout
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 1.4.4
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-08-07 06:59 UTC by outring
Modified: 2016-04-13 18:24 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description outring 2015-08-07 06:59:04 UTC
When setting IsPullToRefreshEnabled to false while refresh in progress, refresh is stopped, but padding at top of the list created by UIRefreshControl remains. It seems that UIRefreshControl.EndRefreshing() is not being called before it got removed by IsPullToRefreshEnabled=false.
Comment 1 Rui Marinho 2015-10-09 06:59:34 UTC
Can you try with 1.5.1-pre1 and see if you still have this problem? 
If you verify it's working ok, please close the issue. 

Thanks
Comment 2 Samantha Houts [MSFT] 2016-04-13 18:24:00 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
 
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team