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.
Created attachment 12912 [details]
When removing/adding children in a grid, the z-order of the children is different on Android vs. iOS.
For example, if you add a child to index 0 of a Grid's children on Android, it will be the bottom-most drawn element (behind everything).
When doing the same thing on iOS, the 0 index child is the top-most drawn element (in front of everything).
**Steps to Reproduce:**
1. Run the attached sample on an iOS simulator.
2. Press the button
3. Notice that the "text is" (green) view moves to the top of the drawn elements.
4. Repeat the same steps on an Android simulator.
5. Notice that on Android at step #3, the green view moves to the back, behind all other elements.
The view that is moved to index 0 of the grid's children is rendered in a different order on each platform.
The 0 index child is expected to be the bottom most element in the drawn order (Android is doing this).
**Build Date & Platform:**
Should be fixed in 1.5.2-pre1
GREAT thanks! I will test it when 1.5.2 is out
I have checked this issue with Xamarin.Forms 1.5.2-pre1 and its working fine.
I am getting same behavior with Android and iOS.
Hence closing this issue.