lAdan wrote:Can eValid interact with page elements that are invisible?
Yes, eValid can do that.
In fact, we have seen a couple of situations in which, because the application was so complex, we had to synchronize playback based on the content of a field that is tagged as "invisible."
Briefly, if the field is in the DOM, whether it conveys information to the face of the browser or not, eValid can interact with it.
This can be a very powerful capability, particularly when you are faced with having to convert a "recorded from life" script into one that works on a structural basis. In many cases web application designers put some little bits of information in the page and mark them as invisible...just as a kind of place keeper.
Harmless to do that certainly, but if you can find such a field or element it makes finding a pivot point for a structural passge very simple. What we've found is that, even when the page is constructed dynamically, the invisible elements remain present. Which is perfect as a synchronization pivot.
eValid Support