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 21782 [details]
When a Cell's context menu is opened (via swipe), opening another context menu is blocked, which is the wanted behavior. But when opening a Cell's context menu and navigating away, the menu stays open and blocks all ListViews from opening context actions. Even when the page with the ListView gets popped, it is even worse, because there is no chance to navigate back and close the menu, leaving the App in this state until forcibly killed by the user.
# Steps to reproduce
Start the sample iOS app.
Open a context menu in the list, then navigate to another tab, try opening context menus there.
# Expected results
The context menus in the other tabs can be opened as well.
# Actual result
# Additional info
This commit https://github.com/xamarin/Xamarin.Forms/commit/cc0eb5ba4326de96a52c0318a61b89c3bcb098e5 added the blocking of context actions via a static field. There needs to be some checking if it is the same ListView instance.
*** This bug has been marked as a duplicate of bug 55588 ***