Bug 23060 - ListView does not respond to touch at bottom 48 px
Summary: ListView does not respond to touch at bottom 48 px
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-09-16 12:44 UTC by Cody Beyer (MSFT)
Modified: 2015-02-05 06:22 UTC (History)
6 users (show)

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

Sample application demonstrating issue (2.53 MB, application/x-zip-compressed)
2014-10-07 02:45 UTC, Dustin

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:

Description Cody Beyer (MSFT) 2014-09-16 12:44:18 UTC
With a ListView such as:

public class MapMenuPage : ContentPage
public MapMenuPage()
var listView = new ListView()
VerticalOptions = LayoutOptions.FillAndExpand
listView.RowHeight = 40;
listView.SetBinding(ListView.ItemsSourceProperty, "Contents");
listView.SetBinding(ListView.SelectedItemProperty, new Binding("SelectedItem", BindingMode.TwoWay));
listView.ItemTemplate = new DataTemplate(typeof(MapFilterCell));

Content = new StackLayout
VerticalOptions = LayoutOptions.FillAndExpand,
Children = { listView }

The bottom 48 px do not respond to any sort of touch, independent of row height.
Comment 2 Dustin 2014-09-16 20:29:48 UTC
Please note this occurs where MapMenuPage (above) is inside a NavigationPage which is the Master in a MasterDetailPage, inside a TabbedPage.

TabbedPage --1st tab--> MasterDetailPage --Master--> NavigationPage --> ContentPage --> ListView

I am only seeing this bug in the above configuration. Touches work fine for my pages with the configuration TabbedPage --> NavigationPage --> ContentPage --> ListView, so it must have something to do with having a ListView as Master inside a MasterDetailPage.
Comment 3 Ram Chandra 2014-10-06 11:45:57 UTC
I have checked this issue but I am unable to reproduce this issue.

Could you please provide sample application and build information? So that we can reproduce this issue at our end.
Comment 4 Dustin 2014-10-07 02:45:21 UTC
Created attachment 8326 [details]
Sample application demonstrating issue

I've managed to narrow down the issue in my own code and create a simple sample app to demonstrate exactly where the problem is.

The issue is caused by this line StyledTabbedPageRenderer.cs:

this.TabBar.Translucent = false;

Commenting this out fixes the issue.

I'm -guessing- that ListView doesn't allow touches in the tabbed area at the bottom of the screen when TabBar.Translucent is true, and that for whatever reason, this region is moved up (instead of being removed or disregarded) when TabBar.Translucent is false and the list view is inside the master page of a master-detail layout. The result is a list view that doesn't respond to touches in its bottom most tabbed-bar sized region.
Comment 5 Ram Chandra 2014-10-07 10:51:17 UTC
I have checked this issue with attached sample project and I am able to reproduce this issue.

I observed that when I set the "this.TabBar.Translucent = false;" the last option of the list view is not selected/highlighted. If I set true to "Translucent" property I observed that it the last item of list view is highlighted.

Screencast: http://www.screencast.com/t/zx3fdw596lh

Environment Info:

=== Xamarin Studio ===

Version 5.5 (build 227)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
	Mono 3.10.0 ((detached/633e444)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000020

=== Apple Developer Tools ===

Xcode 6.0.1 (6528)
Build 6A317

=== Xamarin.Mac ===

Version: (Business Edition)

=== Xamarin.Android ===

Version: 4.18.0 (Business Edition)
Android SDK: /Users/jatin66/Desktop/Backup/android-sdk-macosx
	Supported Android versions:
		1.6   (API level 4)
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.0   (API level 11)
		3.1   (API level 12)
		3.2   (API level 13)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: c6bcfc8
Build date: 2014-10-05 21:42:57-0400

=== Build Information ===

Release ID: 505000227
Git revision: 7b721eeec7a2fa4c4f4de0ecd2aed4dc25edac95
Build date: 2014-10-02 15:53:38-04
Xamarin addins: 99ed56b428b31eba1efaace4d82188d6f334e6ca

=== Operating System ===

Mac OS X 10.9.5
Darwin Jatin66s-iMac.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 6 Jason Smith [MSFT] 2015-02-05 06:22:58 UTC
This happens on iOS if you place pages in the hierarchy in orders it does not like. iOS has a very specific UX pattern that you are expected to adhere to.

MasterDetailPage ---> TabbedPage --> NavigationPage --> CarouselPage --> ContentPage

You may omit a page type at any level, but that is the precedence order on iOS. We allow you to pack them in other ways, but you can end up with results like this where the platform is eating the bottom 48px. Unfortunately this is controlled by UIKit. Things are a little more flexible on phone than tablet.