xamarin/Xamarin.Forms

[UWP] StackLayout content inside TableSection gets clipped

Open

#3,664 opened on Aug 26, 2018

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
e/4 :clock4:help wantedinactivep/UWPt/bug :bug:up-for-grabs

Repository metrics

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

Description

Description

The content of a StackLayout inside a TableSection gets clipped by the amount of outer margin applied to the StackLayout.

Steps to Reproduce

Put this into a page (it needs to be in a TableView, not just the StackLayout itself):

<TableView Intent="Settings">
  <TableRoot>
    <TableSection Title="Memory">
      <ViewCell>
        <StackLayout Orientation="Horizontal" Margin="10,0,10,0">
          <Label Text="Faster" VerticalTextAlignment="Center" HorizontalOptions="Start" />
          <Slider Maximum="3" Minimum="1" HorizontalOptions="FillAndExpand" Margin="10,0" />
          <Label Text="Nicer" VerticalTextAlignment="Center" HorizontalOptions="End" />
        </StackLayout>
      </ViewCell>
    </TableSection>
  </TableRoot>
</TableView>

Expected Behavior

Right end of the slider visible.

Actual Behavior

Right end of the slider is clipped.

Basic Information

  • Version with issue: 3.1.0.697729
  • Last known good version: n/a
  • Platform Target Frameworks:
    • UWP: 17134

Screenshots

untitled-1

Contributor guide

Research direction
Investigate the layout measurement behavior of StackLayout inside TableSection on UWP platform, focusing on how margins are applied and how clipping occurs. Check the UWP renderer for TableView and ViewCell.
Tech stack
csharp
Domain
frontend
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.
Clear
Prerequisites
Xamarin.Forms
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70