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 32290 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 12151 [details]
With a StackLayout that has the following "VerticalOptions = LayoutOptions.CenterAndExpand", images can extend beyond the lower bounds of the StackLayout.
This only appears to happen in the latest version of Forms and works as expected in previous versions (tested with 1.3.3).
## Steps to reproduce
1. Download attached sample
2. Make sure the Forms package is >= 1.4.3
3. Run on an emulator such as a Nexus 4
4. Once the app is loaded, rotate it to landscape to see the effect more clearly
## Expected result
Image should respect it's AspectFit and not overflow beyond the bounds of the StackLayout.
## Actual result
Image overflows beyond the bounds of the StackLayout.
To add to the report, it does not matter what VerticalOptions value is selected for the StackLayout and the overflow behavior occurs with any of the available Aspect settings. I do have to specify a MinimumHeightRequest in order to get the middle StackLayout to not just take up the whole vertical space occupied by its content. Could it be that the image it calculating its display height prior to the StackLayout's MinimumHeightRequest being taken into consideration?
Created attachment 12285 [details]
Created attachment 12286 [details]
This appears to still be occurring as of 220.127.116.1192.
Still present on 2.1
Behaves the same/still present on 2.5