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 for Bug 30900 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 11506 [details]
Project to reproduce this bug
This is an issue on devices with a hardware DPAD (Tested on an Intermec CN51)
We have been observing some wired behavior when navigating XF applications using the DPad on our CN51. Such behavior include instances where the focus seam to be "locked" in an invisible state preventing the user from navigating through the page.
I managed to reproduce such an instance by creating an application with two pages. The second page contain a label and two entry views inside a StackLayout:
Steps to reproduce:
1) Build and run the attached project on a device with a DPAD (tested on an Intermec CN51)
2) click the button no navigate to the second page.
Pressing the up/down buttons on the dpad moves the focus between the actionbar back button and some view not visible. This makes it impossible to navigate the page using the dpad buttons.
If an entry view is selected (using touch) the dpad can be used to navigate the page UNTIL the back button in the actionbar receives focus. After this point the navigation is again stuck between the back button and some invisible view.
using the dpad buttons should switch focus between the two input fields and the actionbar back button.
If the two first views on the second page (the label and the first entry) is swapped the dpad work as expected.