Hello Aranta,
Thanks for raising this issue.
I encountered the same problem, and indeed UIA mode fixed it for me, but I was trying to find a solution to the usual web element clicking using 'navigate' not working.
What I managed to find out by a lot of trial and error (at least in my web automation case via Chrome), is that although the website navigation worked as such (selecting drop downs, clicking 'tabs' to open other section of the page etc), the clicking into text fields did not.
BPC process seems to have partially 'lost' the context of the web app.
I fixed it by mapping the web app render context window in Win32 mode, then using 'navigate' to click in the centre of the window, which seems to have refocused BPC. (Using 'activate' action in 'navigate' did not seem to work to achieve this effect. The Chrome window was activating, but 'navigate' was still not working.)
After that, the 'navigate' started working as expected with the text fields, and i was able to click into the desired field, and use 'send keys' to populate it.
It's a 'dirty workaround', but I wanted to have a backup automation so my primary text entry is using UIA, with the Web automation being the backup.
Hope this helps!
(PS - The 'browser extension port (31924)' issue is a bit annoying, when you have to restart the machine/VM to test Chrome automation in 'production' (control room) or 'development' mode.)
Best Wishes,
Marcin
------------------------------
Marcin Dabrowski
------------------------------