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.
Created attachment 23328 [details]
We have a pretty complex layout for our ViewCells, consisting of Grids and StackLayouts inside ContentViews. The whole thing looks as follows:
| | <title> |<i>|<i>|<i>| | (a)
| +-----------------------+---+---+---+ |
| | | | | | |
| | | |
| | <actual content (colspan=4)> | | (*)
| | | |
| | | | | | |
(a) (*) (a) (a) (a) (a)
(a) ..... auto-sizing
(*) ..... star-sizing
When there is a Label inside that "actual content", which is a ContentView, the Label will be cut off on the right when it should wrap. The sample is boiled down to the minimum code necessary, resulting in two stacked Grids with 2 colums and the ContentView having a colspan of 2. Both removing the ColumnDefinitions or the outer Grid will make it render correctly, so the error seems to originate from this combination.
Xamarin.Forms 18.104.22.1686-pre6: BAD
I was able to reproduce this issue with the attached project. The issue is still occurring with the 22.214.171.124-nightly build. I will confirm the report and we will investigate further.
However, I did notice that if you define a RowDefinition with auto height for the outer Grid, the issue was resolved in the repro project. So this might be a potential workaround for your project in the meantime.
This is now tracked on GitHub: https://github.com/xamarin/Xamarin.Forms/issues/1343