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 54012 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 20855 [details]
When executing application on Windows 10 desktop, additional margin is added below last UI control, when MasterBehavior is set to Default or SplitOnLandscape.
When executing application on Windows 10 desktop with MasterBehavior set to Popover, no additional margin is added.
Platform: Xamarin.Forms 126.96.36.199-pre5
Operating System: Windows 10.0.10240.16725 (Full desktop version)
Hardware: HP ElitePad 900 tablet.
Please see attached screenshots and solution for issue reproduction.
Created attachment 20856 [details]
MasterPage without margin after last UI Control
Created attachment 20857 [details]
MasterPage with margin after last UI Control
Thanks for the reproduction. It requires a further look but could be related in some way to the other one filed which involves the MDP.
Regression fixed by https://github.com/xamarin/Xamarin.Forms/pull/862 blocked investigation of this issue for a while.
On Windows Phone devices there is the inverse reaction. Instead of adding margin, it substracts it, so the bottom-most elements cannot be interacted with, because they're below the screen bounds.