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.
When using a physical keyboard on any of
UWP on desktop
UWP on phone
hitting Tab or Shift-Tab whilst on an Entry view does NOT trigger the Completed event, whilst hitting Enter/Return does.
On WinPhone 8.1 RT running in the emulator (I cannot check on a physical device currently due to a deployment issue), hitting Tab or Shift-Tab does trigger the Completed event. Whilst hitting Enter/Return should trigger the Completed event, hitting Tab or Shift-Tab should not do so.
I just looked into this and it unfortunately appears as if WP8.1 devices simply don't return Tab key presses, or rather that it registers them as Enter key presses in the KeyRoutedEventArgs Key value. SendCompleted fires upon the press of an Entry key in the EntryRenderer, so any time Tab is pressed, it's going to unfortunately treat it like Enter was pressed instead, which explains why the Completed event is triggering. On UWP, Tab is simply ignored (and presumably handled by the system itself).
It seems that this is just a quirk of the 8.1 on the phone, for whatever reason, and I'm not sure there's any way around it off of the top of my head, as even the global key presses via CoreWindow still seem to treat it as Enter. I think that there could be some improvement of documentation to clarify this particular behavior, however.