Bug 41420 - [UWP] Layout bug when placing Label inside Grid inside Grid
Summary: [UWP] Layout bug when placing Label inside Grid inside Grid
Status: RESOLVED DUPLICATE of bug 42559
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.2.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-06-01 04:10 UTC by Dominik Weber
Modified: 2017-02-21 20:56 UTC (History)
3 users (show)

Tags: ac
Is this bug a regression?: ---
Last known good build:


Attachments
test project (229.76 KB, application/x-zip-compressed)
2016-06-01 04:10 UTC, Dominik Weber
Details


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:
Status:
RESOLVED DUPLICATE of bug 42559

Description Dominik Weber 2016-06-01 04:10:46 UTC
Created attachment 16151 [details]
test project

When placing a Label in two nested Grid views with autoheight there is a layout bug which causes the label to only display the first row of text on UWP. On iOS the label is rendered correctly.

This is a fairly complicated (and possibly highly specific) layout - please see the attached test project.
Comment 1 Samantha Houts [MSFT] 2017-02-21 20:56:50 UTC

*** This bug has been marked as a duplicate of bug 42559 ***