Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

Initialize UIautomation tree from an element whose ClassName is Chrome_RenderWidgetHostHWND. Accessability Insights

Ask Question

I need for get UIelements using "UIautomation" technology from another programms in windows OS. Some programms has "chrome-like" browsers for content rendering. The methods are get element (like c# AutomationElement.FromPoint / FindAll) return browser element with ClassName "Chrome_RenderWidgetHostHWND" and Name like a "Chrome Legacy Window". But i need the content elements in that browser.

I found out that, programm "Accessibility Insights" can do it!

Run application, "Microsoft Teams", for example

Run "Accessibility Insights"

Move mouse on "Microsoft Teams", we get "Chrome Legacy Window"

After any mouse click (left/right) on target programm ("Microsoft Teams") provoke rebuild UI tree

Then UIautomation technology can get all inner UI elements in browser.

"Accessibility Insights" source code is https://github.com/microsoft/accessibility-insights-windows I studied it very carefully, but not found code, that provide rebuilding (or, initializing?) inner UI elements.

Any one can help me? What i should to do for win my task - get inner UI elements in chrome-like browsers at another programm on windows OS?

If you've read to the end, thank you

Accessibility Insights for Windows doesn't interact directly with the UI Automation system. It builds on Axe.Windows ( Source code ), which queries and exposes the UI Automation properties. In the case you're describing, Axe.Windows is walking the UI Automation tree in response to a UIA_AutomationFocusChangedEventId message from the UI Automation framework. That notification gets handled by the onFocusChangedEventForSelectingElement method of FocusTracker.cs . Hopefully that will be enough to get you started.

--Dave Tryon (Accessibility Insights team)

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question . Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .