Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
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.
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
Created attachment 24745 [details]
Content Page with the bugged tableview
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.
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.
Any chance anyone can think of a work around for this? Big problem in my app at the moment.
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.