Using the example code in the attachment:
*** Let's say that there are many Route Row's, but that they are Not uniquely named, and we do not want to use numeric's in our xpath (ie. Row 0) because they change.
*** And we want to access a specific Cell 1 'Cell Description Row 0' element
*** Luckily the Cell 2 does have a unique text value e.g Text='Required Data'
*** Therefore an Rxpath of
Code: Select all
//Table/Row[@accessiblename='Row 0']/Cell[@accessiblename='Description Row 0']
is not good enough.
* If I was using regular xpath I would do this:
* Begin with focusing on
Code: Select all
//Row[@Cell~'WorkItemComplete' and @Text='Required Data']
* Then build the xpath backwards using []brackets to focus on the large area:
Code: Select all
//Table[Row[@Cell~'WorkItemComplete' and @Text='Required Data']]/Cell[@accessiblename='Description Row 0']
So as you can see. it is a very useful and powerful aspect of regular xpath.
So to reiterate my original questions : )
Why does Rxpath have this limitation?
And can it be overcome?
You do not have the required permissions to view the files attached to this post.