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 19515 [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 App.
2. Select the "REPL" button from the bottom left corner of the app window.
3. Select the whole pane
4. Observe the Name property in Inspect
The Name property is empty for the REPL pane of the app
Narrator Behavior: Pane
The Name property should be specific.
Eg: REPL app window
Visually impaired users will not get to know the purpose of the REPL app window as the screen reader will not announce anything when the user arrives at the control. Providing the name property enables the compatibility with the Screen Reader, which may be used by people with disabilities.
This is fixed in the upcoming 1.3 release.
Created attachment 24763 [details]
Name property is not descriptive
Needs to be reactivated
I’m not sure we *can* set the Name property of that—it is created by the Internet Explorer control, which we have no power over. Reopening anyway, I can have a second look.
Created attachment 24800 [details]
I did more research on this this morning, and this is *not* something we can fix.
If you look at the screenshot, this is how Internet Explorer presents itself to UI automation--the URL pane is the parent of the actual document. The `<title>` tag of the document is set as the name of its pane, but its parent is always a pane with the URL set as the name.
I will add a <title> to our HTML so that it is a little more descriptive, but otherwise, this is an "upstream" issue.
As per Ryan's comments closing this bug and filed a new bug(Bug 17503975) to track this issue.