Bug 32956 - Setting ListView.SelectedItem to null does not remove list item highlight when list item is tapped multiple times quickly
Summary: Setting ListView.SelectedItem to null does not remove list item highlight whe...
Alias: None
Product: Forms
Classification: Xamarin
Component: Android (show other bugs)
Version: 1.4.4
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Rui Marinho
Depends on:
Reported: 2015-08-11 08:35 UTC by Mike
Modified: 2017-08-07 18:39 UTC (History)
6 users (show)

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

Example Project (261.69 KB, application/x-zip-compressed)
2015-08-11 08:35 UTC, Mike

Description Mike 2015-08-11 08:35:01 UTC
Created attachment 12445 [details]
Example Project

Steps to reproduce:
1. Run the attached project
2. Tap a list item 2 or more times very rapidly
3. The App will open a blank page
4. Return to listing page
5. The list item is still highlighted even though ListView.SelectedItem was set to null in OnAppearing
Comment 1 Paul DiPietro [MSFT] 2015-08-11 11:42:26 UTC
With the reproduction example provided, this is occurring in both iOS and Android when using the most recent version of Forms. The delay is almost completely necessary for reproducing the issue as described.
Comment 2 Chris King 2016-04-13 18:42:32 UTC
Comment 3 adrianknight89 2016-11-11 03:21:33 UTC
See https://github.com/xamarin/Xamarin.Forms/pull/520
Comment 4 Rui Marinho 2017-02-06 12:05:30 UTC
Should be fixed in 2.3.5-pre1
Comment 5 Neha Kharbade 2017-07-04 10:24:42 UTC
Verified on latest build of xamarin.forms , its working as expected. 

hence marking it as verified. 

Gist link - https://gist.github.com/nehaKh/a3c3dddd8a8627dc79ff3d21aed40f32

Screencast link - https://www.screencast.com/t/1VxffTw3
Comment 6 Rui Marinho 2017-07-28 16:58:31 UTC
We need a new fix for iOS..
Comment 7 Rui Marinho 2017-07-28 17:37:13 UTC
https://github.com/xamarin/Xamarin.Forms/pull/1073 for the iOS fix
Comment 8 Rui Marinho 2017-08-07 18:39:35 UTC
Should be fixed on 2.4.0

Note You need to log in before you can comment on or make changes to this bug.