Bug 38770 - RaiseChild and LowerChild do not work on Windows
Summary: RaiseChild and LowerChild do not work on Windows
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.3.5
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jimmy [MSFT]
URL:
: 56844 57610 ()
Depends on:
Blocks:
 
Reported: 2016-02-15 16:20 UTC by Charles Petzold
Modified: 2017-08-23 19:45 UTC (History)
14 users (show)

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


Attachments
repro project (310.33 KB, application/x-zip-compressed)
2017-05-26 23:47 UTC, Jimmy [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

Comment 1 Simon Chopin 2016-11-16 15:20:30 UTC
I noticed the same behaviour. To illustrate, see

https://github.com/laarmen/XamarinFormsGenericApp/tree/raise_lower_child_uwp_bug
Comment 2 Simon Chopin 2016-11-16 15:27:50 UTC
Also, versions: Xamarin 4.2.1.58, Forms 2.3.2.127
Comment 3 Florian CHAUX 2017-01-23 14:14:15 UTC
What's news on this issue ?
Comment 4 Ryan Dixon 2017-02-09 16:40:50 UTC
Was this meant to have been fixed as of 2.3.3.180?
I can still seem to reproduce the issue...

http://pastebin.com/jvPti84g
Comment 5 Jimmy [MSFT] 2017-05-26 23:46:25 UTC
*** Bug 56844 has been marked as a duplicate of this bug. ***
Comment 6 Jimmy [MSFT] 2017-05-26 23:47:19 UTC
Created attachment 22526 [details]
repro project

I am updating this report to indicate that this is still an issue and also affects UWP apps. I've attached the repro project from bug 56844 to the report.

### Version Tests
2.3.5-pre3  BAD
2.3.4.247   BAD
Comment 7 Harikrishnan 2017-06-07 02:29:17 UTC
Am experiencing the same issue in the latest version of Xamarin. When will this be fixed?
Comment 8 Evgeniy Zverev 2017-06-07 11:09:48 UTC
Same here, the issue hits me both with UWP and Windows Phone 8.1/Windows 8.1 apps.
Comment 9 Paul DiPietro [MSFT] 2017-06-08 21:34:18 UTC
https://github.com/xamarin/Xamarin.Forms/pull/981
Comment 10 Paul DiPietro [MSFT] 2017-06-20 13:45:33 UTC
*** Bug 57610 has been marked as a duplicate of this bug. ***
Comment 11 Nicholas Bauer 2017-08-07 07:32:25 UTC
I'm not clear on what the behavior is here that doesn't work, but it may be the same as this. I've noticed that if I add a new child (Child1) to a layout, then try to raise another child (Child0), Child1 will still be above Child0. The next time RaiseChild is called for Child0, Child0 does get placed above Child1.

I only see this behavior for UWP, not Android.
Comment 12 Nicholas Bauer 2017-08-07 07:35:42 UTC
Note: I can't just call RaiseChild twice in a row; it may require adding a new object first.
Comment 13 Samantha Houts [MSFT] 2017-08-23 19:45:24 UTC
Should be fixed in 2.4.0-pre1. Thank you!