We had a process stop working with a selector exception, when I investigated it using ‘edit target’ the selector was not able to validate.
When I removed the selector to try to re-make it, I was not able to identify individual elements of the webpage, only the complete window was selectable.
I added a new activity and when trying to create the new selector I’m not able to identify individual elements, so I cycled ‘UI Framework’
Now suddenly even the Default UI Framework is able to identify elements.
Whats even more confusing is that the selector of the activity that returned the initial exception also works, without having any changes to it.
What is causing this and how do we keep this from happening again?
Did you have any recent upgrades on the browser…some behavioural differences are observed after the latest upgrades in the browser…and for now few workarounds also are provided
Or it might be the case that the extension is not loaded or is turned off