Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Page.UseSafeArea="true" not respected on all pages inside a CarouselPage #3837

Open
jantanis opened this issue Sep 19, 2018 · 1 comment
Open
Labels
a/layout e/4 🕓 4 help wanted We welcome community contributions to any issue, but these might be a good place to start! inactive Issue is older than 6 months and needs to be retested t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!

Comments

@jantanis
Copy link

Description

When creating a CarouselPage with more than 2 ContentPages within it. The Page.UseSafeAre is only respected on the first two pages.

Steps to Reproduce

  1. Create an empty Xamarin.Forms project
  2. Change the MainPage to a CarouselPage
  3. Add more than 2 ContentPages, with each ContentPage having this:
    xmlns:ios="clr-namespace:Xamarin.Forms.PlatformConfiguration.iOSSpecific;assembly=Xamarin.Forms.Core" ios:Page.UseSafeArea="true" and some content on it.
  4. Start iOS simulator for an iPhone X(s/r)

Expected behavior

It should be expected that the "notch" area will be discarded and that the content starts below it.

Actual Behavior

For the first two pages the notch area is discarded. But for every other page it is not.

Basic Information

Xamarin.Forms 3.2.0.839982
Simulator device: iPhone XR iOS 12.0

Screenshots

First two pages:
screen shot 2018-09-19 at 21 15 07

Every other page:
screen shot 2018-09-19 at 21 14 57

@pauldipietro pauldipietro added this to New in Triage Sep 19, 2018
@rmarinho rmarinho added the e/4 🕓 4 label Sep 25, 2018
@rmarinho rmarinho moved this from New to Ready For Work in Triage Sep 25, 2018
@samhouts samhouts added this to To do in Other Ready For Work Oct 15, 2018
@samhouts samhouts removed this from Ready For Work in Triage Oct 15, 2018
@samhouts samhouts added the inactive Issue is older than 6 months and needs to be retested label Mar 19, 2019
@samhouts samhouts added help-wanted up-for-grabs We welcome community contributions to any issue, but these might be a good place to start! help wanted We welcome community contributions to any issue, but these might be a good place to start! and removed help-wanted labels Jun 28, 2019
@adambarath
Copy link
Contributor

adambarath commented Dec 20, 2019

Has anybody got a fix for this issue? Still reproducable in XF 4.4

@samhouts samhouts removed the inactive Issue is older than 6 months and needs to be retested label Feb 6, 2020
@samhouts samhouts added the inactive Issue is older than 6 months and needs to be retested label Jul 17, 2020
@samhouts samhouts added this to the 5.0.0 milestone Aug 13, 2020
@samhouts samhouts added this to To do in vNext+1 (5.0.0) Aug 14, 2020
@samhouts samhouts removed this from the 5.0.0 milestone Nov 2, 2020
@rmarinho rmarinho removed their assignment Aug 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a/layout e/4 🕓 4 help wanted We welcome community contributions to any issue, but these might be a good place to start! inactive Issue is older than 6 months and needs to be retested t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!
Projects
Development

No branches or pull requests

5 participants