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 19579 [details]
Please find the attached screenshot
• Windows 10.
• Version 1067.
• Build 14393.607.
Visual Studio and Xamarin:
• VS 2017 RC Enterprise.
• Xamarin For VS 126.96.36.1990.
• Xamarin Profiler 1.0.4
Pre -Requisites: Build and Deploy Xamarin Application into Android Emulator
1.Launch Xamarin profiler through Visual Studio.
2.Navigate to the "General" tab and select any tab from the existing "Available Instruments" from "Choose an Instrument Template" window.
3.Try to access the navigation pane beside the tool bar under "Inspector View" section in “Xamarin Profiler" window. [screenshot]
Unable to access the navigation pane beside the tool bar in "Inspector View" section.
To expand the content and check, the user should be able to access the navigation pane beside the tool bar in "Inspector View" section.
The Is Keyboard Focusable and Has Keyboard Focus must be "True".
Visually impaired users who are dependent on keyboard navigation find difficult when the UI elements are not accessible while navigating through the application.
Fixed in XamarinProfiler.Windows.Installer.1.5.99-127
Verified the issue in version 188.8.131.52
Issue got fixed. Hence closing bug.
VF per Salieu Njie on 7/8/17. Updating BZ as their contractor did not have access permissions to change the bug state.