Best practices for Web Page elements
What are the experienced users using to recognize the objects on a webpage? I have inherited a project that is using the tree model. This seems OK for a relatively stable website, bu...
Forum Discussion
In an ideal world, it seems best to have a unique identifier for all of the elements on the webpage, so I can find
an object by the identifier (presumably the ID string) and operate on it
from there, or throw an error if the object does not exist.
Problems with this are:
1) not having control over whether objects have unique identifiers or not
2) possible increased execution time to stop and find every object. Has this been a problem for anybody?
We avoid the namemapping/alias features like the plague and use the approach you describe here exclusively. I wrote a Jscript library for our purposes specifically to make this easier.
Performance has never really been an issue. Occasionally there is an issue finding unique properties to identify a control, but it is very rare.