This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 44176 - InputTransparent fails if BackgroundColor not explicitly set on Android
Summary: InputTransparent fails if BackgroundColor not explicitly set on Android
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-09-12 02:53 UTC by adrianknight89
Modified: 2017-03-23 17:27 UTC (History)
8 users (show)

See Also:
Tags: AC
Is this bug a regression?: ---
Last known good build:

repro (211.65 KB, application/zip)
2016-09-12 02:53 UTC, adrianknight89

Description adrianknight89 2016-09-12 02:53:09 UTC
Created attachment 17412 [details]

Setting InputTransparent="False" does not work on Android if the background color is not set or if it is set to Transparent. The color must be set to a **non-transparent** color in order for taps not to propagate down.

On iOS, all is fine.

Please see repro.

XF / Samsung S6.
Comment 1 Gabor Nemeth 2016-09-16 09:16:48 UTC
I confirm this issue. I have experienced in one of my apps. I had to set InputTransparent to false and IsEnabled to true on a ListView to be able to disable user interaction.

In this example if the BackgroundColor is set to non-transparent, but Opacity is also set - for example - to 0.5, the ContentView let tap events across. Even if IsEnabled is set to false on it.

Comment 2 adrianknight89 2016-09-16 14:31:30 UTC
Please see my PR:
Comment 3 Samantha Houts 2016-09-30 23:18:03 UTC
Should be fixed in 2.3.4-pre1. Thank you!
Comment 4 Parmendra Kumar 2016-11-28 15:20:33 UTC
I have checked this issue with Xamarin.Forms 2.3.4-pre1 and I am still getting same issue with Android and on iOS its working fine.


Hence reopened this issue.

Please have a look screencast and let me know If I have missed anything to verify this issue.
Comment 5 adrianknight89 2016-11-28 15:25:16 UTC
A better fix should be, but it needs to be merged.
Comment 6 Jon Goldberger 2017-01-28 00:41:16 UTC
There are a couple of other seemingly related bug reports that are not resolved in the 2.3.4-pre1.


Thought I would bring it up so you can see if the issues are related and whether they may be fixed by the pull request noted in comment 5 above.
Comment 7 Rui Marinho 2017-03-23 17:27:44 UTC
Should be fixed on 2.3.5-pre1.

Note You need to log in before you can comment on or make changes to this bug.