Bug 59839 - iOS 11 - TabbedRenderer - Element overwrites native safe area
Summary: iOS 11 - TabbedRenderer - Element overwrites native safe area
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-09-29 08:59 UTC by Tim Holzkämper
Modified: 2017-09-29 14:33 UTC (History)
2 users (show)

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

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 for Bug 59839 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Tim Holzkämper 2017-09-29 08:59:00 UTC
We've tried to get a custom tabbed page renderer dereived from the TabbedRenderer to utilize the new safe area layout guide. But the base ViewDidLayoutSubview method causes the element and therefore the native view to fill the entire screen.

This method gets called twice during the layout process. In the first call the safe area insets are [44, 0, 34, 0] (that's correct) but in the second call the insets are [0, 0, 0, 0] (filling the entire screen). This results in the custom tabbar overlapping the software home button on the iPhone X since the bottom of the safe area layout guide is equal to the bottom of the screen.

Other renderers probably show a similar behaviour.
Comment 1 Paul DiPietro [MSFT] 2017-09-29 14:33:30 UTC
A reproduction project to see your custom renderer would always be welcomed here, but we are aware that some changes in general need to be made surrounding the iPhone X and the safe area/notch.