xamarin/Xamarin.Forms

[Bug][iOS][Android] SwipeViewItems cut off on one or more sides

Open

#8,782 opened on Dec 6, 2019

View on GitHubContributor guide
 (1 comment) (1 reaction) (1 assignee)C# (1,926 forks)batch import
a/swipeviewe/1 :clock1:help wantedin-progressinactivet/bug :bug:up-for-grabs

Repository metrics

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

Description

Description

I've defined multiple SwipeItemView objects in a SwipeView. However, the problems are:

  • On iOS, the first SwipeItemView is cut off on the left hand side.
  • On both iOS and Android, the right most SwipeItemView is cut off on the right hand side.

Steps to Reproduce

  1. Run the attached sample on iOS.
  2. Browse to the SwipeView custom SwipeItem page.
  3. Swipe from the right on "What's 1+1?".

Expected Behavior

The two SwipeItemView objects are fully shown, without being cut off on either side.

Actual Behavior

On iOS, the first SwipeItemView is cut off on the left hand side. On both iOS and Android, the right most SwipeItemView is cut off on the right hand side.

Basic Information

  • Version with issue: 4.4-pre3
  • IDE: VSMac 8.3.10
  • Platform Target Frameworks:
    • iOS: 13.2
    • Android: API 28

Screenshots

Simulator Screen Shot - iPhone X - 2019-12-06 at 14 45 14

Screenshot_1575643554

Reproduction Link

SwipeViewDemos.zip

Contributor guide

Research direction
Investigate the layout logic in SwipeView's platform renderers for iOS and Android. Check how SwipeItemView widths are calculated and whether they are affected by padding or margins. Trace the measurement and arrangement steps when swiping.
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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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.FormsMobile UI Layout
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60