Bug 57982 - ListView context actions called with the wrong binding context
Summary: ListView context actions called with the wrong binding context
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-07-06 16:02 UTC by Daniel
Modified: 2017-11-29 07:30 UTC (History)
3 users (show)

Tags: ac uwp listview contextactions bindingcontext
Is this bug a regression?: ---
Last known good build:

Sample that reproduces the bug (74.55 KB, application/x-7z-compressed)
2017-07-06 16:02 UTC, Daniel

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 57982 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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Daniel 2017-07-06 16:02:39 UTC
Created attachment 23358 [details]
Sample that reproduces the bug

Removing an entry from the list, followed by adding a new one and trying to remove this new entry results in its context actions being called with the wrong binding context (or just with the wrong ViewCell).
The attached sample should reproduce the bug.
Comment 1 Jimmy [MSFT] 2017-07-06 23:16:54 UTC
I was able to reproduce this issue with the attached project so I am confirming this report and we will investigate further.

### Version Tests   BAD
2.3.5-pre6  BAD   BAD
Comment 2 Daniel 2017-07-08 13:22:44 UTC
This also happens when replacing entries (setting a new value on an existing index).
Comment 3 OBATA Akio 2017-11-29 07:30:19 UTC
duplicate of Bug 42999?