As discussed here are some points regarding the New UiExplorer tool. We feel that it does not work as well as the older version and other improvements could be made:
You have multiple properties belonging to objects but you are now only able to select based on a few attributes. Previously we could easily add attributes such as checked/visibility which at times could help us identify an element or more information about an element. The selector editor is now restricted to the point that you cannot make these changes and whilst you can add them manually you do not always know the exact syntax required.
Validate selector previously highlighted the actual element on the screen. Now it just says that the element is valid but how do you know that it is actually picking up the correct item? What if something has a very similar name and the id changes so actually you are picking up the incorrect element but UiPath Explorer thinks it is valid.
I have always thought that if you change the selector in UiPathExplorer you should be able to press a button at the top to swap the selector with your new information. Instead you have to copy and paste the new text back into UiPath.
With regards to the post by Cosmin at Renaming minor UIPath elements - I didn’t actually realise that this is what was happening. I think that this should be included within the Standard UiExplorer, perhaps you could have a “Compare Selectors” button at the top which would allow you to first select an element and store the attributes, then reload the page or load a similar page and select a second element to compare with. This would help you to see which attributes change and which remain the same. Additionally then you could select Wildcard (e.g. must exist but can be anything) or partial text (e.g. Internet Explorer *) or remove attribute (already can do this). I feel this warrants a further conversation but something for you to think about.