Bug 60659 - [iOS] SetUseSafeArea causes bottom of page content to be cutoff displaying page background
Summary: [iOS] SetUseSafeArea causes bottom of page content to be cutoff displaying pa...
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.4.0
Hardware: Macintosh Mac OS
: Highest normal
Target Milestone: ---
Assignee: Rui Marinho
URL:
Depends on:
Blocks:
 
Reported: 2017-11-14 03:20 UTC by David Ortinau [MSFT]
Modified: 2017-11-16 11:52 UTC (History)
3 users (show)

Tags: safe area, ac
Is this bug a regression?: ---
Last known good build:


Attachments
sample project (63.46 KB, application/zip)
2017-11-14 03:20 UTC, David Ortinau [MSFT]
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description David Ortinau [MSFT] 2017-11-14 03:20:42 UTC
Created attachment 25682 [details]
sample project

ContentPage background is red. The ListView should obscured the red always. With SetUserSafeArea enabled, the red is display unless scrolling. See video.

https://www.screencast.com/t/yuiSyWxST

Project attached. This is the ItemsPage.xaml.

2.4.0 Latest : BAD
2.5.1.74177-nightly : BAD

Turning off SetUseSafeArea returns the expected design/layout behavior.
Comment 2 Rui Marinho 2017-11-16 11:52:06 UTC
Should be fixed on 2.4.0 SR6 or 2.5.0 sr1