Bug 26264 - Under Android, RaiseChild() and LowerChild() appear to be reversed.
Summary: Under Android, RaiseChild() and LowerChild() appear to be reversed.
Status: RESOLVED DUPLICATE of bug 25591
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-01-22 00:02 UTC by philip
Modified: 2015-01-30 13:37 UTC (History)
5 users (show)

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 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:

Description philip 2015-01-22 00:02:37 UTC
Under Android, RaiseChild() actually lowers the child in terms of visibility (it moves to be below other children in the stack). I assume this is the opposite of what is intended.  I did not test it on other platforms and only tested it with AbsoluteLayout as the container.
Comment 1 philip 2015-01-22 23:17:11 UTC
This already appears to be fixed in
Comment 2 Jon Goldberger [MSFT] 2015-01-30 13:37:30 UTC

*** This bug has been marked as a duplicate of bug 25591 ***