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 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.
I am using a Label inside a StackLayout, that seems to be ignoring the YAlign value on WinPhone. When I use the following, the text within the available height is shown at the top, not at the bottom of the available height.
Label titleLabel =
FontAttributes = FontAttributes.Bold,
HeightRequest = 75,
HorizontalOptions = LayoutOptions.StartAndExpand,
Text = contentPage.Title.ToUpper(),
XAlign = TextAlignment.Start,
YAlign = TextAlignment.End
On Android and iOS, this works as expected, but on WinPhone both TextAlignment.End and TextAlignment.Center are ignored for YAlign.
I have checked this issue and I am also getting the same behavior.
Observation: I have checked this issue and observed that the YAlign property is not working for Label control. I tried to set the "YAlign = TextAlignment.End" and YAlign = TextAlignment.Center but it always shows the Start.
Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Installed Version: Professional
Xamarin 3.11.666.0 (ebae43a)
Xamarin.Android 126.96.36.199 (5f55a9ef61c11b6ce0890bc91e4c71b1b92be214)
Xamarin.iOS 188.8.131.52 (67b390d0d1bd741582cf7b7fd3ffea08583a3f83)
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team