Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Xamarin Forms' RaiseChild and LowerChild methods (Xamarin.Forms.Layout) have no effect in the UWP platform.
### Sample App
This sample app is a trivial Xamarin Forms app that demonstrates the problem.
### Steps to Reproduce
1) Download, open and run the sample Xamarin Forms app in the UWP emulator
2) Click the "Raise Red" button to raise the red box on screen to the top
3) Click the "Lower Blue" button to lower the blue box on screen to the rear
### Expected Behavior
The red box, which begins on the bottom of a stack of three boxes, raises to the top of the stack.
The blue box, which begins on the top of the three-box stack, lowers to the bottom of the stack.
Here is a screenshot from the Android emulator (where this works fine) showing what the screen should look like after performing steps 2 and 3 above.
### Actual Behavior
Here is a screenshot from the UWP emulator showing the original screen...pressing ANY "Raise" or "Lower" button has no effect. Note that both RaiseChild and LowerChild work as expected on Android and iOS.
=== Visual Studio ===
Visual Studio Enterprise 2017 v4.7.02046
=== Xamarin ===
=== Xamarin.Forms ===
=== OS ===
Windows 10 Professional, v10.0.15063
*** This bug has been marked as a duplicate of bug 38770 ***