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 and Windows 8.1 RT, if the user uses the keyboard to move the selection in a ListView, ItemSelected is not fired. It should be.
Not supporting keyboard usage will cause problems with accessibility.
Should be fixed in 2.3.2-pre1. Thank you!
Still a problem in 220.127.116.11
The expected behavior is that ItemSelected will be fired each time the selection moves from one ListView item to another, which on UWP is going to result from using the cursor up and cursor down keys when a keyboard is available.
The actual behavior is that ItemSelected is only fired when the Enter/Return key is pressed. Hitting Enter/Return or space should fire ItemTapped, not ItemSelected, so the actual behavior is wrong in two ways - neither ItemSelected nor ItemTapped is fired when expected.
This should be resolved as a part of this PR which adds the accessibility support: https://github.com/xamarin/Xamarin.Forms/pull/713