Experiencing

[jamesm1 (James)]

I believe I am experiencing this bug:

Broken selectors after Chrome/Edge update to version 114.0.1823.37

The latest Chrome and Edge updates (114.0.1823.37) introduced a breaking change to the way support for Active Accessibility is enabled. This causes automation processes to fail when trying to interact with the following browser screens: Print popup PDF viewer Observed behavior Following the browser update, it is no longer possible to identify web elements using Active Accessibility (AA) mode with UIAutomation activities. Example of selector that no longer works because of this issue: <wnd…

My organization uses Orchestrator and has a firewall that blocks access to official channels. However I was able to manually download and Install packages, install to Orchestrator, and pull this down to my UI Studio. I am on 2022.4.2 version of UI path (not easy to upgrade via my org) Currently I arm running the following libraries:

According to the bug above, 22.4.9 should fix these issues. But I am unable to target the ‘save as’ button. I get the following symptoms. When I Use the current values (before the activity broke) I can try and highlight the target and I see this:

see next post

When I try to ‘Indicate Element I see’
see next post

I’m assuming these are the symptoms of this bug, but I don’t understand why my newest version of UiPath.UIAutomation.Activities didn’t fix it. Any suggestions?

[jamesm1 (James)]

[jamesm1 (James)]

[Yoichi]

Hi,

It may be chrome/edge 117 matter.
Can you check the following topic?

In Chrome and Edge v117 the Active Accessibility support is broken for IFRAMEs and PDFs

Starting with Chrome and Edge v117 we are seeing a new bug that affects Active Accessibility support for web pages that contain IFRAMEs or PDF documents. This bug means that <ctrl /> selectors for those web pages might fail. Available workaround If you are affected by this issue, the immediately available workaround is to start the browser with this flag added to the command line: --force-renderer-accessibility=complete Since UiPath.UIAutomation.Activities v23.8.0-preview this can be easily …

Regards,

[jamesm1 (James)]

I installed UiPath.UIAutomation.Activities = 23.10.2 per that bug report and STILL all the same symptoms.

[Yoichi]

HI,

In my environment, (Studio 23.4.2+UIAutomation23.10.2) works well

Is UiPath Extension installed correctly?
How about choose explicly from Auto to AA in UiFramework?

Regards,

[jamesm1 (James)]

Does not work in my Environment (22.4.2 + UIAutomation23.10.2)
UiPath Extension is installed.

How do you get to that ‘selection options’ panel?

[Yoichi]

HI,

It’s modern UiAutoamation. If you use Classic, can you try to press F4? It changes cyclically like Default,AA and UIA
Or use Mdoern UiAutoamtion : UseApplciationBrowser and NClick etc.

Regards,

[jamesm1 (James)]

Sorry I am pretty new at this. I’m picking up someone else’s bot. I see this. F4does nothing and F6 starts the program

[Yoichi]

HI,

Can you try to press F4 when indicating element (The following window)?

Regards,

[jamesm1 (James)]

Ok I see it now (probably looks different because of the older version, also it was on my first monitor (I have 3) ):

All versions (Default, AA, UAI) only show the entire box highlighted (I assume the same symptoms of the previous two bugs mentioned above.

lf I am NOT on a webpage but rather an Edge ‘new window’ screen (not a webpage) I can select elements offset from the element I’m trying to target:

[jamesm1 (James)]

Ok I THINK I found it (and maybe a new bug). If I disable my other monitors I can target this correctly. I will try this. Thanks for your help (and patience)