Browser mode Click backwards compatibility for MV3 vs MV2 extension

[EmmanuelTsitsir]

When running a Click stage in Edge Browser mode  using an element with JavaScript in the "href" attribute, MV3 extension throws error but MV2 extension executes the stage correctly.
A workaround flow for MV3 is:

1.  Read the "href" value of the element and if it includes JavaScript:

2. Use "Set Attribute" to set the "href" value in the "onclick" attribute

3. Use "Set Attribute" to set empty value in the "href" attribute

4. Run Click Element via browser mode
Since this code will be required for every browser click to be able to handle this scenario (JavaScript in "href"), I would suggest to incorporate this flow in BluePrism code in order to ensure the backwards compatibility of Click for the MV3 extension.

[sumire]

On this issue, if anyone has tried Blue Prism Browser Automation Agent for Manifest V3 Extensions | Blue Prism Portal , let me know if it works.