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 14498 [details]
I have a ListView with caching strategy set to RecycleElement, where each cell has a certain number of context actions implemented with MenuItems.
In Android, when the user long presses on a cell the actions are shown and the background color of the selected cell is changed. The problem is that if the user starts scrolling down the list while a cell is selected, after the selected cell goes out of the screen, another cell at the bottom appears with the background color changed, as if it was selected, and this happens repeatedly (if one has enough list items), and this is confusing. The issue is not present when using the RetainElement caching strategy, to this should be a problem related to the recycling of cells.
A sample project has been attached.
I can still reproduce this issue on Forms 2.3.2-pre1 with the attached repro. And it actually crashes now if you keep scrolling around the list.
This report appears to be a duplicate of bug 39476. On further testing, I can't reproduce the original issue using the attached project with Forms 2.3.1.
The crash I am experiencing is a different issue.
Confirming that this was fixed with bug 39476. The crash mentioned in Comment 2 is bug 42832. Thank you!
*** This bug has been marked as a duplicate of bug 39476 ***