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 19597 [details]
Please find the attached screenshot
• Windows 10.
• Version 1067.
• Build 14393.607.
Visual Studio and Xamarin:
• VS 2017 RC Enterprise.
• Xamarin For VS 184.108.40.2060.
• Xamarin Profiler 1.0.4
Pre -Requisites: Build and Deploy Xamarin Application into Android Emulator
1.Launch Xamarin profiler through Visual Studio.
2.From "Choose an Instrument Template" window navigate to the "General" tab and select any instruments tab from the existing "Available Instruments”.
3.Select the "Call Tree" tab from the "Instrument Detail Area" section and navigate to the "Stack Trace" tab in "Inspector View" section, observe the focus jump when we tab the second data item under "Heaviest Stack Trace".
while navigating the tab items under "Heaviest Stack Trace" the keyboard focus jumps to "Instrument Detail Area" section for the second tab.
while we tab the interactive elements should not perform any action without user interaction with keyboard.
Triggering changes or activating functionality without direct user choice can be extremely problematic for screen reader users and those with cognitive disabilities.
Fixed in version 220.127.116.11 (master)
Author: Jose Miguel Torres
Commit: 682e30c8e3ec36ed358d0daefac14e6a620ef104 (xamarin/profiler)
Verified on 18.104.22.168 (master).Hence marking it as verified.
Verified on 22.214.171.124 (master).Hence marking it as verified.
VF per Salieu Njie on 7/8/17. Updating BZ as their contractor did not have access permissions to change the bug state.