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 52684 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
Created attachment 19908 [details]
Sample showing issue
In the sample app I have a listview with 20 items. When you tap an item, it updates the item and then navigates to a different page. When you navigate back, the listview is positioned back to the top, regardless of where the item you tapped on was in the list.
Tested on 126.96.36.199. Note this does not happen on iOS or Android.
Thanks for the reproduction. For some reason I can actually have the list disappear completely if the window is vertically compressed and I scroll down and then navigate back. Setting this to confirmed for now and wondering (at a glance) if it's related to 48682.
True that the behavior is different but I'm wondering if the cost converging the behavior is worth the price in maintenance. Right now, I'm inclined to say that if a ListView's contents are replaced the ListView's position may be at zero or at an offset.
Consider the case with uneven rows where item n is visible which is m pixels down from item 0. When the ItemsSource is replaced should the ListView keep item n visible or should it be m pixels down even though n might not be visible due to the new distribution of row heights? I could see arguments either way. Instead of putting a stake in the ground I'd prefer to leave the behavior undefined and off the work around of updating the individual items with new data. Is there a reason that is onerous in your more scenario?
I'll also circle back and see what the team thinks.
Paul, please let us know if you're unable to work around by updating items in the list as opposed to replacing them.
@Chris King, We can, though I feel like this should get fixed since that is just a workaround.
The problem is not about the ListView, it's about the page design, Currently the page will dispose the old page when navigate the new page, that's why when you back the old think not keep the original status(basically it will initial again).
We should make UWP behavior the same as iOS and Android