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 42501 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 16639 [details]
On WP8, controls inside a ScrollView that is nested in 2+ layouts will not be rendered. However, if the ScrollView is empty, then it will be rendered (if it has a Height/WidthRequest). Even more interesting is that if the ScrollView has an (empty) layout, then it will also be rendered. But adding a control to the inner layout will cause the issue again. So it only occurs with control child elements.
I looked into the issue further by creating a custom renderer for the ScrollView and when the issue occurred I observed:
- ArrangeOverride is not called
- ElementPropertyChanged is not called for ContentSize
### Steps to Reproduce
1. Run the attached project
### Expected Results
The ScrollView will be rendered.
### Actual Results
The ContentPage is empty.
### Testing Info
Tested on Forms 126.96.36.199 and 188.8.131.52-pre2. This issue started ocurring in Forms 2.1.
I can confirm this bug:
In our project we are having a deep hierarchy of controls (also known as control composition). It means a lot of work for us to restructure the complete UI code just because of this bug. Is it possible to handle this bug with high prio or is there a useful workaround?