I would love to have a new feature, where you can map objects using the xpath. The problem with the current object mapping is, that it only supports a given set of tags, which gets harder and har...
To expand on this discussion, the current name mapping also causes trouble with dynamic websites like ours, where the DOM changes a lot based on user input. Take for example the selector "//ul/button", which can map to a button in any unordered list which appears.
In our case, each object on the site has a unique ID, save for a few react-objects which didn't want to play along. Therefore, all name mapped objects are mapped manually, either using their IDs or mapped as a child object of the closest parent with an ID.
Although improving the internal algorithm is a great first step, I imagine it would be very difficult to make it work with dynamic websites like ours, as Testcomplete can't see all elements of the site at any given time. As such, giving the user the ability to explicitly state which selectors to use or not use when automatically name mapping using CSS selectors and XPath would be greatly appreciated.