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 19627 [details]
Please find the attached screenshot
• Windows 10.
• Version 1067.
• Build 14393.607.
Visual Studio and Xamarin:
• VS 2017 RC Enterprise.
• Xamarin For VS 18.104.22.1680.
• Xamarin Profiler 1.0.4
Pre -Requisites: Build and Deploy Xamarin Application into Android Emulator
1.Launch Xamarin profiler-> "Choose an instrument template" window->
2. Observe the localized control type for the following interactive elements:
a. General/Advanced menu item (vertical tab item)
b. Instruments list items (i.e. Allocations, Cycles, Time Profiler, Performance. etc.) of “Choose an instrument template" window
In inspect, localized control type is "custom'.
Narrator: The narrator is announcing as "custom"
Localized control type should be “tab item”.
Users with disabilities will be misguided by the custom localized control type.
This row is inside a ListView, we don't use TabItems into a ListView, but custom templates in oder to represent the data. So, I guess the target of this bug is the Narrator to be able to narrate the content of that ListView row, isn't it? please clarify this.
This question has been clarified.
Fixed in XamarinProfiler.Windows.Installer.1.5.99-153
VF per Salieu Njie on 7/8/17. Updating BZ as their contractor did not have access permissions to change the bug state.