Bug 35863 - Listview has an unwanted top and bottom spacing in Android 6.0
Summary: Listview has an unwanted top and bottom spacing in Android 6.0
Status: RESOLVED DUPLICATE of bug 35122
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.5.1
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-11-14 15:35 UTC by Marko
Modified: 2015-11-14 17:45 UTC (History)
1 user (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 DUPLICATE of bug 35122

Description Marko 2015-11-14 15:35:12 UTC
There's a ListView bug (at least with 1.5.1.) on Android 6. On top and below the content of the ListView, there's a spacing with the size of the screen height. So, when you open a page with a ListView, you see nothing and have to scroll down to see the actual content.

You can simply reprocue it with the the FormsGallery Sample in the Emulator (Google APIs Level 23, Google APIs Intel Atom x86_64 Image)

http://forums.xamarin.com/discussion/comment/164867/#Comment_164867
Comment 1 Paul DiPietro [MSFT] 2015-11-14 17:45:41 UTC

*** This bug has been marked as a duplicate of bug 35122 ***