Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 43425 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 17051 [details]
On UWP, the Footer of a ListView is displayed at the bottom of the page and overlapped by the device's soft buttons if present.
### Steps to Reproduce
1. Run the UWP project in the attached repro solution
### Expected Results
The Footer will be right below the last item in the ListView.
### Actual Results
The Footer is at the bottom of the page and will be overlapped by the soft buttons.
### Testing Info
Tested with Forms 126.96.36.199 and 188.8.131.52-pre1
Is there a particular emulator/device you're using where the soft buttons are overlapped? It seems like the footer being at the bottom of the page is just a UWP thing; if you use a ListView with a footer in a regular UWP app, it puts it at the bottom as well.
I inadvertently noticed that putting it in a NavigationPage seems to do the trick, though?
Yeah I also noticed that the footer being anchored to the bottom is UWP behavior.
I tested on a Lumia 950 and it overlaps when _not_ inside a NavigationPage. However, I tested with just using a Label with VerticalOptions = End and it was also overlapped so I don't think this is specific to the ListView, but to the Page.
I too experience this problem. Is there any fix or workaround?