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 19550 [details]
• Windows 10.
• Version 1067.
• Build 14393.607.
Visual Studio and Xamarin:
• VS 2017 RC Enterprise.
• Xamarin For VS 184.108.40.2060.
• Xamarin Inspector 1.0
Pre -Requisites: Build and Deploy Xamarin Application into Android Emulator
1.Launch Xamarin Inspector.
2. Arrive at Help menu and Hit enter.
3. Tab through About Xamarin Inspector and Hit enter.
4. Try to close pop-up message/child window using keyboard.
Note: Similar Issue observed in below location.
1. Launch Xamarin inspector -> Click on Tools menu -> Select Options -> Try to Access Close, Maximize,
Keyboard focus is not going to close button and cannot close using Escape key form keyboard.
Close Button should be Accessible with keyboard and 'Escape' key should be able to close 'child window'/Pop-up
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.
I couldn't find a way to get the close buttons in the tab order, seeing as they're part of the menu bar, but implementing Escape-to-close was trivial.
This is fixed in the upcoming 1.3 release.
Verified the bug and the issue is fixed.