Element attributes beginning with "Parent …" allow an identification of elements by considering their context. Unfortunately a rather simple but insecure method of generating this attribute's value has been implemented ("Parent Window Title" in this example): all window titles of all elements that are direct ancestors are baked into a single string, separated by just a space character. If an application has 3 windows with one window being a child to the root window and another window being a child to the child window, the "Parent Window Title" value for the "child-child" window will be something like "SubChildWindow ChildWindow RootWindow <UNKNOWN>". These issues will come with this implementation: 1. Space character can't be used as separators between window titles as window titles often contain spaces themselves. This way it is not possible to separate the window titles anymore. Also, BP seems to just concatenate the titles with additional spaces, resulting in values that have 2 space characters as separators. Hardly anything but wildcards can be used on something like that, which again results in a very unprecise matching. I suggest that a standardized format is used instead of just adding everything to this string and randomly putting spaces between it. 2. adding "<UNKNOWN>" to this string if the window title could not be determined is insecure as this could be interpreted as a real window title. Instead, another solution should be choosen to mark an unreadable title.
... View more