Bug 24030 - InputTransparent is implemented wrong on Android
Summary: InputTransparent is implemented wrong on Android
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-10-23 19:31 UTC by luca.barbieri
Modified: 2015-05-29 10:44 UTC (History)
5 users (show)

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

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 luca.barbieri 2014-10-23 19:31:04 UTC
In the Java code of FormsViewGroup, you have this code:

package com.xamarin.forms.platform.android;

public class FormsViewGroup extends ViewGroup
  public boolean onInterceptTouchEvent(MotionEvent ev)
    if (this.inputTransparent) {
      return false;
    return super.onInterceptTouchEvent(ev);

This is wrong, because it means that touch events are passed to children of Xamarin.Forms.View instances that have InputTransparent set to true.

You should instead replace "return false" with "return true" in that code, so that the touch event is intercepted and thus not passed to children.

Might be a duplicate of #22796, but you said you fixed it in the 1.3.0 branch, and it's still broken in the 1.3.0 tech preview.