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.
On UWP, the user can navigate between cells in a ListView using the cursor keys on the keyboard. However, neither hitting Space nor Return result in the currently focused cell having its Tapped event fired or OnTapped called.
I have a custom cell that inherits from ViewCell, and that contains a StackLayout, that contains another StackLayout, that contains two Labels, so none of the views within the ViewCell are themselves tapable using the keyboard, but the ViewCell should be as it is focusable / selectable.
Without keyboard support on Windows desktop, accessibility cannot be implemented fully, which could put us in contravention of equality legislation.
Should be fixed in 2.3.2-pre1. Thanks!
I'm looking forward to giving it a try - keyboard support is great for both accessibility and for power users. It'll be good to be able to work using the keyboard on Windows (and hopefully Android and iOS later on :-) )
@Samantha_Houts - Just tested against 220.127.116.11 . Still not working, on UWP or WinRT 8.1 . Also tried it on Android using a physical keyboard - no success there either.
John -- It looks like the code which was added to resolve this issue (for at least the case of the enter key) was in place, but for some reason removed between 2.3.2 and 2.3.3 when further additions to accessibility features were put in. I'll find out what happened here.
Assigned to you because bug you were last to resolve bug before it was re-opened.
Should be fixed on 2.4.1-pre1