Captured Element Twice

bug-report

#1

We can create the same element using different approaches (css and xpath).

Captured same element twice accidentally. Would like to have a system warning for this if possible.


#2

Hey @manoj.madusanka!

We have already got a check in place, preventing Ranorex Selocity from sending two identical selectors, which covers most accidental duplicates – but it could be helpful indeed, to warn the user in when two different selectors point to the same element.

We will discuss the priority of this case and possible solutions within the team, thank you for the input!