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 for Bug 60475 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I am not sure if this is expected behaviour, but it would be good to have some clarification regardless.
1) Create a Grid with one row and column both using Star GridLength
2) Insert any dummy content into this row/column
3) Insert a new row definition using Grid.Children.Insert at row index 0
Existing content is merged down with the row the originally were placed on, in this case the new index 1
The content is being drawn onto the new row as the layout cycle progresses
If you can confirm that this is indeed a bug and simply that the Grid needs to respect the CollectionChange events on the Observable then I don't mind doing the PR myself!