[Bug] Can't Overlap a Button with any view under certain circumstances

[WarBorg]

Description

Having the button and another view in front of the button on a layout (AbsoluteLayout, Grid,.. "kind of layout that allows overlap") and all of that into a ScrollView and into a NavigationPage the button will always be on top

There is also a related issue with this, having the button on a layout (AbsoluteLayout, Grid,.. "kind of layout that allows overlap") with something in front of it without the navigation page and the scrollview it will look ok but when I click the button multiple times it will come in front of the other visual elements but even if it looks like it came in front visually, the zone where the element was overlapping is not clickable on the button

If the button is disabled the visual overlap is not happening

related to #3543

Steps to Reproduce

1. Add a button on a layout (AbsoluteLayout, Grid,.. "kind of layout that allows overlap")
2. Then add another view (ActivityIndicator, Image, Notification Badges, text, ..) on the layout
3. Enclose this into a scroll view
4. Enclose the page into a NavigationPage
5. The Button always in front if enabled

Expected Behavior

The expected hierarchy of the visual stack would be:

• Button would be on the back of the visual stack.
• The other view would be on the front of the visual stack.

Actual Behavior

The button is stuck on the front of the visual stack.

Basic Information

• Xamarin Forms Version: 4.5.0.396
• Platform Target Frameworks: Android
  • Android Target SDK: 10.0
  • Android test device: emulator running Android 9 api 28

Screenshots

Reproduction Link

https://github.com/WarBorg/TestActivityButtonXamForms

Workaround

switch to UseLegacyRenderers

[PureWeen]

@WarBorg this one is a bit tricky and we still don't have the best solution for it..
#7300

The problem here is that button has an elevation on it. When button was using a legacy renderer it was wrapped in a viewgroup with an elevation that just stayed zero so it was always at the same relative elevation as everything else.

A few ways you can fix this without revertting

• set the layouts to CompressedLayout.IsHeadless="True" which will allow some work around code we have on android to fix what elevations it can
• wrap the button in a stacklayout or a grid so that it basically simulates having a viewgroup

[WarBorg]

@PureWeen thank you for your answer

since we cant use the CompressedLayout.IsHeadless="True" because we are changing visibility and backgroundcolor on the elements inside the layouts I choose to use the second method and wrapped the button in a stacklayout and seems that did the trick :D