xamarin/Xamarin.Forms

FlexLayout Grow Property issue

Open

#3,797 opened on Sep 17, 2018

View on GitHubContributor guide
 (2 comments) (1 reaction) (1 assignee)C# (1,926 forks)batch import
a/flexa/layoute/6 :clock6:help wantedinactivet/bug :bug:up-for-grabs

Repository metrics

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

Description

Description

When the FlexLayout's Grow Property is set, if the view is too long it will occupy other view's space even the padding of it's parent...

Steps to Reproduce

youdu 20180917093143

Expected Behavior

The view which is set Grow property dno't occupy the other view's space

Actual Behavior

The view which is set Grow property occupied the other view's space

Basic Information

  • Version with issue:
  • Last known good version:null
  • IDE:vs2017
  • Platform Target Frameworks:
    • iOS: 11.4
    • Android: 8.1
    • UWP: null
  • Android Support Library Version:
  • Nuget Packages:3.1.0.583944
  • Affected Devices:

Screenshots

screenshot_1537146916

Reproduction Link

null

Contributor guide

Research direction
Examine the FlexLayout Grow property implementation in Xamarin.Forms to understand how it affects layout calculations, especially when views exceed their allocated space. Look at the layout engine's handling of Grow and potentially related properties like Shrink or Basis. Check if there are any existing tests for Grow behavior.
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.FormsC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60