Bug 36002 - Visibility issue with dynamic content of a ContentView (since Forms 2.0)
Summary: Visibility issue with dynamic content of a ContentView (since Forms 2.0)
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-11-18 09:57 UTC by Philipp
Modified: 2015-11-23 11:53 UTC (History)
5 users (show)

Tags: ac
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:

Description Philipp 2015-11-18 09:57:10 UTC
When we dynamically change the content of an invisible ContentView, it does not become visible with the next IsVisible = true.

See the following project https://github.com/philippd/ContentView-Bug.git which shows this issue.

- Tap on Update
- Tap on Hide
- Tap on Update again

-> The content is not visible

- Tap on Update

-> The content becomes visible

Workaround: If the ContentView is set to visible before changing the content, everything works fine.

NOTE: We have this issue since upgrading to Xamarin.Forms 2.0, everything was working fine before
Comment 1 Paul DiPietro [MSFT] 2015-11-18 11:36:39 UTC
I'm seeing the same described behavior on the version prior to 2.0, as something to take note of.
Comment 2 Rui Marinho 2015-11-23 08:40:47 UTC
This is fixed with
Comment 3 Philipp 2015-11-23 10:59:03 UTC fixed the issue in my repro case I sent you. In the real app however, we use an animation to fade the element in. This still is not working correctly.

See the updated version of the project here: https://github.com/philippd/ContentView-Bug.git 

The workaround for me is still the same: Setting the ContentView to visible and opacity to zero before changing the content works.

Should I open a new bug for this?
Comment 4 Rui Marinho 2015-11-23 11:53:43 UTC
Please do, i will look at it.