Bug 39472 - Android inconsistency when Opacity of element is 0; input is still blocked
Summary: Android inconsistency when Opacity of element is 0; input is still blocked
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.1.0
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-03-08 23:03 UTC by Cliff Cawley
Modified: 2016-09-24 03:25 UTC (History)
4 users (show)

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


Attachments
Sample project attached which demonstrates issue (48.48 KB, application/zip)
2016-03-08 23:03 UTC, Cliff Cawley
Details


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 39472 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:
Status:
CONFIRMED

Description Cliff Cawley 2016-03-08 23:03:54 UTC
Created attachment 15321 [details]
Sample project attached which demonstrates issue

## Steps to reproduce

1. Download attached sample
2. Build All and run on iOS/Android
3. Try to click the button

## Expected result

Opacity of 0 allows tap events to pass through, acting as though you'd set the control invisible

## Actual result

iOS:
As expected, opacity of 0 allows tap events to pass through

Android:
The fully transparent layout will block all events. To work around if you're setting a control to 0 opacity, you need to on android set the view invisible too.


## Notes
For example you might be animating the fading of a view out. On Android you currently have to remember to also set it invisible once the fade is done. You don't have to do this on iOS.

When you fade the view back in you need to set it Visible first on Android.
Comment 1 Jason Smith [MSFT] 2016-03-10 20:40:52 UTC
Yeah this is a known distinction between how these platforms handle input
Comment 2 Jason Smith [MSFT] 2016-03-10 20:40:58 UTC
Yeah this is a known distinction between how these platforms handle input
Comment 3 adrianknight89 2016-09-24 03:25:17 UTC
I worked on a different problem: https://github.com/xamarin/Xamarin.Forms/pull/344

Not sure if it would have any affect on this problem. You probably need to re-test once the PR is merged.