Bug 24029 - Clickable is being always set on Android views, which is wrong
Summary: Clickable is being always set on Android views, which is wrong
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Rui Marinho
Depends on:
Reported: 2014-10-23 19:05 UTC by luca.barbieri
Modified: 2015-05-21 04:40 UTC (History)
4 users (show)

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:05:28 UTC
Currently you are setting Clickable = true on all Android views.

You should definitely not do anything like this.

1. Setting Clickable means that EVERYTHING including labels eats touch input events.
2. Any ListView with a ViewCell no longer supports normal list item selection, because the children capture the touch events, even if they are just a bunch of labels.
3. Setting Clickable results in View.isActionableForAccessibility() to return true, which is going to screw up accessibility tools.
4. Setting Clickable results in the control being styled as a clickable item, which is obviously wrong if it isn't
5. Setting Clickable results in the control entering PRESSED state upon clicks, which can then change styling etc. which is also obviously wrong if the element is not clickable

You should instead set Clickable if and only if there is a single tap gesture recognizer defined.

Also note that doing handling clicks with single-tap gesture recognizers is wrong as well, but that's a separate bug, filed as #24026.
Comment 1 Rui Marinho 2015-05-21 04:40:22 UTC
This should no longer be the case on the newest release