Bug 34061 - RelativeLayout - First child added after page display does not appear
Summary: RelativeLayout - First child added after page display does not appear
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.5.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Rui Marinho
Depends on:
Reported: 2015-09-18 11:27 UTC by calvin.fisher
Modified: 2015-10-26 10:17 UTC (History)
6 users (show)

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

This page demonstrates the bug (1.82 KB, text/plain)
2015-09-18 11:27 UTC, calvin.fisher

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 calvin.fisher 2015-09-18 11:27:25 UTC
Created attachment 12948 [details]
This page demonstrates the bug

See attached test page.  Tested on iOS implementation.

Expected: every tap of "add popover" button adds a semi-transparent control on top of the layout.

Observed: the first tap does not add anything.  The second tap adds two.  Subsequent taps behave as expected.

This workaround works: adding and removing an invisible child to the relative layout before adding the actual desired view.
Comment 1 Paul DiPietro [MSFT] 2015-09-18 13:33:55 UTC
Updated to and it does what you're describing based on the code you provided.
Comment 2 Rui Marinho 2015-10-07 13:19:16 UTC
Should be fixed in 1.5.2-pre1
Comment 3 Parmendra Kumar 2015-10-26 10:17:32 UTC
I have checked this issue with Xamarin.Forms 1.5.2-pre1 and its working fine.

Hence closing this issue.