cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade to 7.3.2 - Click Action on Buttons/Hyperlink not working in Chrome

uncki2
Level 5

Dear Community members,

Hope you're doing well.

We have recently upgraded to BP 7.3.2 from v6.10.5, we have observed that CLICK action in NAVIGATE stage spied using Browser mode is not working in chrome-based applications.

Highlighting & focus of the element is working; however, action click is not working. Bot was able to click same button / link in BP 6.10.

For interim we have spied the element using UIA mode for clicking so that bot execution can continue.

However, I foresee a serious concern if browser mode can highlight the element but unable to click. Anyone have faced the similar issue before and how to resolve this? Any pointers would be greatly appreciated.

Chrome Version

uncki2_0-1758850320586.png

 

BP Extension

uncki2_1-1758850320593.png

 

Kishlay Singh
Senior Consultant
UOB
Singapore
1 REPLY 1

Check to see if there is JavaScript in the href attribute of the link by doing Right Click > Inspect on the element. You may need to do right click > inspect twice in a row for it to highlight in the Developer Tools pane.

--------------------------------------------------------------------------

Below is only applicable if there is JavaScript in the href attribute of the element.

This is one of the limitations introduced as of MV3 (Manifest Version 3). One of the workarounds is what you implemented which is to use UIA/AA to click it instead. There are one or two other workarounds too.

How do I work around the href JavaScript issue in Browser Automations? :

[BPE] BP-11545 / BP-12841 - Browser interactions with elements that trigger JavaScript fail to run when using Manifest V3 browser extensions :

I'll say this. Based on BP's documentation, it would lead me to think that 7.3.2 and other recent versions shouldn't have this issue, but (from my testing) all of the MV3 versions cannot use browser mode to click links where the href attribute has JavaScript in them, at least not without doing a special workaround.

Here's info about MV3: [IMPORTANT NOTIFICATION] IMPACT OF MANIFEST V3 ON USE OF CHROME AND EDGE BROWSERS AS PART OF BLUE PRISM AUTOMATIONS :


Dave Morris, 3Ci at Southern Company