I forgot to mention about the usage of markup id.
I think this is a less optimize way to find the drag source component,
especially if the page object graph is large.
For example,
If we have the following Page component structure.
Page
- Container1
- Table with a lot of rows
- other component
- Container2
- Table
- rows
- "dragSource"
If we search based on output markup id for drag source, it will have
to visit Container 1 and all its children, before visiting container
2.
By using path (sample path "0:container2:....:dragSource" ), instead
of visitor,
the search will be a matter on how many hop to get to the drag source.
Regards,
Edward Yakop
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
