Bug 60246 - Events on UWP GROUPED Listview have an issue since 2.4
Summary: Events on UWP GROUPED Listview have an issue since 2.4
Status: RESOLVED DUPLICATE of bug 59718
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-18 01:23 UTC by AlanLS
Modified: 2017-10-18 01:51 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

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 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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 59718

Description AlanLS 2017-10-18 01:23:32 UTC
Using Xamarin.Forms.

Events on UWP GROUPED Listview have an issue.

I run and MVVM model. 

When using a GROUPED Listview, items lower in the list seem to trigger multiple "selecteditem" events, usually I get the the item I tapped, PRECEDED by the item in teh list immediately before the pressed one (even across groups).

(note I get similar? results using ItemTapped)

iOS and Android seem to be fine.

This may have been here prior, but noticed only after the 2.4 update.
Comment 1 Paul DiPietro [MSFT] 2017-10-18 01:51:37 UTC
Sounds like 59718. Please refer to that bug.

*** This bug has been marked as a duplicate of bug 59718 ***