Bug 59485 - TableView Multiple Section Navigation Bug
Summary: TableView Multiple Section Navigation Bug
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.4.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-09-14 09:23 UTC by Alex
Modified: 2017-10-04 12:44 UTC (History)
3 users (show)

Tags: tableview, cell, tapped, ac
Is this bug a regression?: ---
Last known good build:

Content Page with the bugged tableview (1.47 KB, application/octet-stream)
2017-09-14 09:24 UTC, Alex

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 59485 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 Alex 2017-09-14 09:23:45 UTC
So the problem I am facing is the tableview not reacting as you would think it does. Attached is a demo of this, just run the project.

Repo steps:
1. Click on the entry input in section one (so they keyboard appears)
2. Scroll to the second section and click the navigation cell (Nav Cell Two) leaving the keyboard open.

You would expect this to navigate you to a new page but the cell does not get selected. Instead it seems to press another cell above it (randomly or the height of the keyboard). Once the keyboard goes away it will work just fine.

Video here: http://recordit.co/5cgV8kTHPA
Comment 1 Alex 2017-09-14 09:24:44 UTC
Created attachment 24745 [details]
Content Page with the bugged tableview
Comment 2 Alex 2017-09-14 09:27:37 UTC
New to this so the attached is now a content page with the tableview inside. If you create a project and run this code you will see the problem. 

If anyone can tidy up my mess in here that would be great.
Comment 3 Paul DiPietro [MSFT] 2017-09-14 16:02:04 UTC
I'll set this to confirmed for now, though it appears that the keyboard being dismissed may be interfering with the tapped gesture firing when the cell is tapped quickly. If your tap holds the cell for anything more than a quarter of a second (possibly even less), the navigation looks to work as expected. This may or may not be entirely expected behavior, but I can't say for certain at this moment until it's investigated further.
Comment 4 Alex 2017-09-21 07:19:00 UTC
Any chance anyone can think of a work around for this? Big problem in my app at the moment.
Comment 5 Alex 2017-10-04 12:44:29 UTC
I have a work around for this problem but its not great. I have created a custom renderer and using UIScrollViewKeyboardDismissMode.OnDrag on the tableview. This will dismiss the keyboard when scrolling through the tableview.