xamarin/Xamarin.Forms

[Bug] [UWP][Android] Grid.WidthRequest=0 ignored when changed during runtime

Open

#6,287 opened on May 23, 2019

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
a/layoute/6 :clock6:help wantedinactivep/Androidp/UWPt/bug :bug:up-for-grabs

Repository metrics

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

Description

Description

When setting the WidthRequest for a Grid at runtime, setting it to 0 is ignored while settig it to positive values works. This occurs on UWP and Android. Works as expected on iOS.

Steps to Reproduce

  1. Open the attached test project
  2. Deploy to UWP or Android
  3. Observe the red rectangle on the left with width of 200
  4. Click the 0px button

Expected Behavior

Red rectangle should disappear.

Actual Behavior

Red rectangle remains at same size

Notes

Click the 1px button to see that changing to a positive value for the WidthRequest works.

Basic Information

  • Version with issue: 4.0.0.425677
  • Last known good version: unknown
  • IDE: Visual Studio 2019 and Visual Studio for Mac
  • Platform Target Frameworks:
    • Android: 9.0
    • UWP: 17763

Reproduction Link

TestGridWidth.zip

Contributor guide

Research direction
Investigate the OnSizeRequest or MeasureOverride methods in the Grid layout to see why setting WidthRequest to 0 is ignored. Check platform specific renderers for UWP and Android.
Tech stack
csharp
Domain
mobilefrontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65