Bug 60769 - iOS ListView item selected event is not firing. Xamarin Forms 2.4
Summary: iOS ListView item selected event is not firing. Xamarin Forms 2.4
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.5.0
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-11-20 12:40 UTC by gelleor
Modified: 2018-04-03 13:12 UTC (History)
4 users (show)

Tags: listview, itemselected, tapgesture, ac
Is this bug a regression?: ---
Last known good build:


Attachments
Example with bug (5.47 MB, application/x-zip-compressed)
2017-11-20 12:40 UTC, gelleor
Details


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 60769 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:
Status:
CONFIRMED

Description gelleor 2017-11-20 12:40:40 UTC
Created attachment 25762 [details]
Example with bug

Listview item selected event is not fired on iOS if ListView container has TapGestureRecognizer bound to it.

Reproduction steps: 
1) create a container view (Stack, Grid, Frame, ContentViev ...)
2) add TapGestureRecognizer to the container view 
3) add ListView inside the container and populate it with items
4) subscribe to ListView.ItemSelected event
5) Run app and click any item in the ListView

Expected result:
Item in the ListView is selected, ItemSelected event is fired

Actual result:
Item in the ListView is not selected, ItemSelected event is not fired
Comment 1 adrianknight89 2017-11-21 00:11:48 UTC
How is this behaving on Android? Sounds like the parent view is trapping gestures instead of gestures bubbling up from child to parent. Issues like this were common a while back, and unfortunately different platforms don't always seem to be acting similarly.
Comment 2 adrianknight89 2017-11-21 00:24:24 UTC
On iOS, I think this is the default behavior. More discussion here: https://stackoverflow.com/questions/5222998/uigesturerecognizer-blocks-subview-for-handling-touch-events

Still though, the lack of consistency across multiple platforms is not good, IMO.
Comment 3 gelleor 2017-11-21 10:01:32 UTC
Android is fine, issue appears right after Ive update Xamarin Forms 2.3->2.4

Now I downgraded to 2.3 and it is fine. So it is definitely not default behavior it is new bug in 2.4. Also checked with 2.5 issue still present
Comment 4 gelleor 2017-11-23 17:46:07 UTC
Any updates guys
Comment 5 gelleor 2017-11-27 09:16:31 UTC
Any updates guys
Comment 6 gelleor 2017-12-01 09:08:41 UTC
Any updates guys
Comment 7 Paul DiPietro [MSFT] 2017-12-01 15:02:42 UTC
We will provide updates as the bug is being investigated and worked on.
Comment 8 gelleor 2017-12-01 16:36:59 UTC
Good, any approximate date?
Comment 9 Paul DiPietro [MSFT] 2017-12-01 16:41:26 UTC
Not at this time.
Comment 10 gelleor 2018-03-22 13:28:44 UTC
How is it going guys, have you fixed this bug already?
Comment 11 gelleor 2018-04-03 13:12:37 UTC
How is it going guys, have you fixed this bug already?
Comment 12 gelleor 2018-04-03 13:12:50 UTC
How is it going guys, have you fixed this bug already?