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 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.
Using XF v188.8.131.52
If we apply InputTransparent property to a control which is defined in a ViewCell, then the behavior is not as expected in case of Android.
In iOS it works fine, but Android is not reflecting the behavior still the click event is functioning.
Any help on this would be appreciated.
Could you please provide the following for investigation?
1. Minimized runnable test case demonstrating the issue
2. Steps to reproduce
3. Full version information
Xamarin Studio Windows: Help > About > Show Details > Copy Information [button]
Visual Studio: Help > About Microsoft Visual Studio > Copy Info [button]
I think this is likely a dupe of https://bugzilla.xamarin.com/show_bug.cgi?id=50992
It seems to be kind of universal that InputTransparent is not working as expected on Android.
If you create a new Forms PCL Xaml solution and replace the Label in the Xaml with:
> Date="2016-07-08" />
> Placeholder="Enter Date"
> InputTransparent="true" />
On iOS clicking on the entry pulls up the date picker, but on Android it does not, you start editing the Entry instead.
(Reported in SO post: http://stackoverflow.com/questions/41877614/xamarin-forms-inputtransparent-doesnt-work-on-android )
*** This bug has been marked as a duplicate of bug 50992 ***