Bug 39429 - Layouts elements missing in & .. display in
Summary: Layouts elements missing in & .. display in
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.1.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-07 20:53 UTC by christine.blanda
Modified: 2016-03-11 04:49 UTC (History)
4 users (show)

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

Test Project (196.26 KB, application/x-zip-compressed)
2016-03-07 21:02 UTC, christine.blanda

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:

Description christine.blanda 2016-03-07 20:53:21 UTC
Run the attached project using Forms, there is a blue title bar on the top of the view.  Upgrade forms to or and the title no longer displays.
Comment 1 christine.blanda 2016-03-07 21:02:23 UTC
Created attachment 15294 [details]
Test Project
Comment 2 Jason Smith [MSFT] 2016-03-11 04:49:38 UTC
So the general bulk of the problem here is not the layout at all but rather your _layout Grid is not parented the way you expect in the newer version of Forms. This is due to the fact that hte XAML loader now correctly determines which Content property to assign to (it always assigns to the ContentPage.Content even if you mask it) where as before it had an error where it would use a masked property. While its an interesting hack, it's 100% not supported :)