xamarin/Xamarin.Forms

Long text in Label inside StackLayout inside AbsoluteLayout results in a out of container drawing.

Open

#7,819 opened on Oct 4, 2019

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)C# (1,926 forks)batch import
a/layoute/3 :clock3:help wantedp/Androidp/iOS 🍎t/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

Suppose master Label lies inside StackLayout inside AbsoluteLayout. If I change text from short to long in Label it does change size but moves other children to draw outside of container (or container does not resize correctly). Although adding additional children to parent container or changing button size produce correct results.

Steps to Reproduce

  1. Use application from Reproduction Link
  2. Change text to long\short
  3. Add one or more buttons
  4. Enlarge first button

Expected Behavior

Height of Label with multiline text scales its parent container correctly.

Actual Behavior

I don't think it is suppose to work like that.

Basic Information

  • Version with issue: 4.2.0.848062
  • Last known good version: unknown
  • IDE: Microsoft Visual Studio Community 16.3.2
  • Platform Target Frameworks:
    • iOS: Default
    • Android: 9.0
  • Android Support Library Version:
  • Nuget Packages:
    • NETStandard.Library v2.0.3
    • Xamarin.Forms v4.2.0.848062
  • Affected Devices:
    • Android Emulator
    • iPhone Simulator

Screenshots

Android

iOS

Reproduction Link

Application uses color coded visual elements backgrounds with round corners to ease debugging. Github

Contributor guide

Research direction
Investigate the layout behavior of Label within StackLayout inside AbsoluteLayout. Focus on how size changes propagate and cause other children to draw outside the container.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Xamarin.Forms
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50