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 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.
Created attachment 19524 [details]
• Windows 10.
• Version 1067.
• Build 14393.607.
Visual Studio and Xamarin:
• VS 2017 RC Enterprise.
• Xamarin For VS 18.104.22.1680.
• Xamarin Inspector 1.0
Pre -Requisites: Build and Deploy Xamarin Application into Android Emulator
1.Launch Xamarin inspector.
2. Try to access REPL, View inspector button using keyboard and observe
Keyboard Focus is not going to REPL, View Inspect buttons.
REPL, View Inspector buttons should be accessible with Keyboard.
Users need to be able to navigate an application and interact with all the UI elements by using a keyboard alone. Users who are dependent on keyboard navigation include those with visual impairments who rely on screen readers and those with dexterity or mobility impairments who cannot use a mouse.
Looked into this briefly:
The editor is eating Tab/Ctrl-Tab when the REPL/Workbook window initially shows up, which makes tabbing around the widgets not work at all. If you pick a different widget and start tabbing around (like a sidebar item), the workbook/view inspector tabs are hit eventually, so they are definitely in the tab order.
This has also been moved to https://github.com/Microsoft/workbooks/issues/136, which combines this issue and https://bugzilla.xamarin.com/show_bug.cgi?id=51834.